End-to-end network encryption from customer on-premise network to customer virtual cloud network using customer-managed keys

ABSTRACT

For end-to-end encryption of a virtual cloud network, a VPN tunnel from a customer device is terminated at a host network headend device using encryption keys secured in hardware and managed by the customer. The network headend device can be a card in a bare-metal server with one or more network virtualization devices. The network headend device is configured to receive a first key provisioned by a customer; receive a first data packet sent from a device of the customer; and decrypt the first data packet using the first key to obtain information. A network virtualization device is configured to receive the information from the network headend device; ascertain that the information is to be sent to a virtual machine in a virtual cloud network; ascertain that data in the virtual cloud network is configured to be encrypted; and encrypt the information with a second key to generate a second data packet before routing the second data packet to the virtual machine.

CROSS-REFERENCES TO RELATED APPLICATIONS

The following two U.S. patent applications (including this one) arebeing filed concurrently, and the entire disclosure of the otherapplication is incorporated by reference into this application for allpurposes:

-   -   application Ser. No. 17/133,526, filed Dec. 23, 2020, entitled        “MECHANISM TO PROVIDE CUSTOMER VCN NETWORK ENCRYPTION USING        CUSTOMER-MANAGED KEYS IN NETWORK VIRTUALIZATION DEVICE”; and    -   application Ser. No. 17/133,523, filed Dec. 23, 2020, entitled        “END-TO-END NETWORK ENCRYPTION FROM CUSTOMER ON-PREMISE NETWORK        TO CUSTOMER VIRTUAL CLOUD NETWORK USING CUSTOMER-MANAGED KEYS”).

BACKGROUND

A virtual cloud network (VCN) is a customizable and private network.Similar to a traditional data center network, the VCN provides controlover a network environment. This includes assigning private IPaddresses, creating subnets, creating route tables, and configuringfirewalls. A single tenant can have multiple VCNs, thereby providinggrouping and isolation of related resources.

Data in a VCN can be encrypted for security. One purpose of encryptionis to convert plaintext data into unintelligible ciphertext based on akey, in such a way that it is very hard (e.g., computationallyinfeasible) to convert ciphertext back into its corresponding plaintextwithout knowledge of the correct key. In a symmetric cryptosystem, thesame key is used both for encryption and decryption of the same data. Insome encryption algorithms, a key length can be 128-bit, 192-bit, or256-bit. In some encryption standards (e.g., Data Encryption Standard(DES) algorithms, message data is encrypted with three passes of the DESalgorithm. 3DES can provide a high degree of message security, but witha performance penalty. The magnitude of the performance penalty candepend on the speed of the processor performing the encryption. The RC4algorithm, developed by RSA Data Security Inc., has become theinternational standard for high-speed data encryption. RC4 is a variablekey-length stream cipher that operates at several times the speed ofDES, making it possible to encrypt large, bulk data transfers withminimal performance consequences. Encryption of network data providesdata privacy so that unauthorized parties are not able to view plaintextdata as it passes over the network.

BRIEF SUMMARY

The present disclosure relates generally to a virtual cloud networks(VCN). More particularly, and without limitation, techniques aredescribed for encrypting data between a customer and a VCN forend-to-end encryption, where the customer manages the encryption key.Instead of terminating a VPN tunnel at a VPN gateway of a host using ashared key, a VPN tunnel from a customer device is terminated at a hostdevice using encryption keys secured in hardware and managed by thecustomer. The device can be a bare-metal server with a networkvirtualization device(s).

In certain embodiments, a system includes a network headend device and anetwork virtualization device. The network headend device is configuredto: receive a first key provisioned by a customer; receive a first datapacket sent from a device of the customer; and/or decrypt the first datapacket using the first key to obtain information. The networkvirtualization device is configured to: receive the information from thenetwork headend device, after the first data packet is decrypted;ascertain that the information is to be sent to a virtual machine in avirtual cloud network; ascertain that data in the virtual cloud networkis configured to be encrypted; encrypt the information with a second keyto generate a second data packet; and/or route the second data packet tothe virtual machine.

In certain embodiments, the system is maintained by a host, and the hostdoes not have access to the first key or the second key; the networkheadend device is configured to be a termination point of an internetprotocol security (IPSec) tunnel formed between the network headenddevice and a customer device; the first data packet is routed throughthe public Internet; the first data packet is routed through a set ofprivate links, without using links in the public Internet; the networkvirtualization device supports an instance of a virtual machine in thevirtual cloud network; the network headend device is a network interfacecard; the network headend device is on a network interface card and thenetwork virtualization device is part of the network interface card; thenetwork headend device and the network virtualization device are in thesame server; the network headend device is dedicated to the customer,such that no other customers of a host use the network headend device;the network virtualization device communicates with a key managementservice to obtain the second key; the customer provisions the first keyin the network headend device using a key management service; thenetwork headend device is a first network headend device and the systemfurther comprises a second network headend device configured to decryptdata from the customer; the network virtualization device is a firstnetwork virtualization device, the virtual cloud network is a firstvirtual cloud network, the system further comprises a second networkvirtualization device, and/or the second network virtualization deviceis configured to receive data from the network headend device andencrypt data received from the network headend device for a secondvirtual cloud network using a third key; the first networkvirtualization device and the second network virtualization device arepart of the same network interface card; and/or the network headenddevice is configured to receive the first key from the customer after ahost authenticates the customer.

In yet other embodiments, a method includes receiving, using a networkheadend device, a first key provisioned by a customer; receiving a firstdata packet at the network headend device sent from a device of thecustomer; decrypting the first data packet, using the first key, toobtain information; receiving, using a network virtualization device,the information from the network headend device; ascertaining that theinformation is to be sent to a virtual machine in a virtual cloudnetwork; encrypting the information with the network virtualizationdevice, using a second key, to generate a second data packet; and/orrouting the second data packet to the virtual machine.

The foregoing, together with other features and embodiments will becomemore apparent upon referring to the following specification, claims, andaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a schematic illustration of one embodiment of a systemfor a network virtualization device.

FIG. 2 is a depiction of one embodiment multiple network virtualizationdevices receiving crypto keys from a key management service.

FIG. 3 is a depiction of one embodiment of a network virtualizationdevice supporting multiple customers with different crypto keys.

FIG. 4 is a flowchart illustrating one embodiment of a process forencrypting data in a virtual cloud network.

FIG. 5 is a flowchart illustrating one embodiment of a process for usingmultiple crypto keys for data encryption for multiple virtual cloudnetworks.

FIG. 6 is a depiction of one embodiment of a virtual cloud networkreceiving data through a VPN gateway.

FIG. 7 is a depiction of one embodiment of a virtual cloud networkreceiving data through a Virtual Cloud Network (VCN) headend.

FIG. 8 is a depiction of an embodiment of one VCN headend supportingmore than one virtual cloud network.

FIG. 9 is a flowchart illustrating one embodiment of a process forend-to-end encryption for a virtual cloud network.

FIG. 10 is a block diagram illustrating one pattern for implementing acloud infrastructure as a service system, according to at least oneembodiment.

FIG. 11 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 12 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 13 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 14 is a block diagram illustrating an example computer system,according to at least one embodiment.

FIG. 15 is a high level diagram of a distributed environment showing avirtual or overlay cloud network hosted by a cloud service providerinfrastructure according to certain embodiments.

FIG. 16 depicts a simplified architectural diagram of the physicalcomponents in the physical network within CSPI according to certainembodiments.

FIG. 17 shows an example arrangement within CSPI where a host machine isconnected to multiple network virtualization devices (NVDs) according tocertain embodiments.

FIG. 18 depicts connectivity between a host machine and an NVD forproviding I/O virtualization for supporting multitenancy according tocertain embodiments.

FIG. 19 depicts a simplified block diagram of a physical networkprovided by a CSPI according to certain embodiments.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofcertain embodiments. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive. The word “exemplary”is used herein to mean “serving as an example, instance, orillustration.” Any embodiment or design described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother embodiments or designs.

A virtual cloud network (VCN) is a customizable and private network. Ahost can provide computing hardware and/or software for a customer toset up a VCN. Typically, the host manages encryption, if any, for a VCN.A customer might not want the host to manage encryption because thecustomer could fear a data breach of the host could compromise customerdata, or the customer might be concerned about how much customer datathe host has access to. This description relates to a mechanism toprovide VCN network encryption using customer-managed keys. Thecustomer-managed keys can be distributed in SmartNICs. A SmartNIC is anetwork interface card (e.g., a network adapter) that offloadsprocessing tasks that a CPU might normally handle. A SmartNIC canperform functions such as encryption, decryption, routing, firewall,etc.

A SmartNIC can be used to support Network Encryption Virtual Functions(NEVFs) with a dedicated crypto accelerator and/or SRAM. The cryptoaccelerator can be used for in-line packet encryption. The SRAM can beused to store encryption keys. A NEVF assigned to a customer virtualmachine (the customer virtual machine is part of the customer VCN) canbe used for virtual machine network traffic encryption and to storeencryption keys. A hypervisor can map a customer virtual machine to anNEVF. Encryption keys can be securely provisioned in the NEVFs incustomer VCN instances (e.g., virtual machines (VMs) and/or bare metal(BM)).

Traffic exchanged between customer VCN instances is encrypted withencryption keys provisioned in NEVFs. Each instance in a VCN share thesame encryption key (e.g., opportunistic encryption). A control planecan provision and/or manage network encryption keys for customerinstances (VMs and/or BMs) in a VCN. The control plane can be used toauthenticate customer virtual functions and provision encryption keysfrom a key management service. Using certificates, the key managementservice and the NIC can securely share customer encryption keys. Thusthe customer can manage network encryption keys (e.g., using applicationprogram interfaces and/or operating system commands). In someconfigurations, unique keys are shared between VM hosts in a VCN. TheNEVF of each VM host stores keys and/or meta-data associated with whichkey to use.

With reference to FIG. 1 , a schematic illustration of one embodiment ofa system for encrypting data for a virtual cloud network is shown. Anetwork virtualization device 100 comprises a first virtualizationengine 104-1 and a second virtualization engine 104-2. Thevirtualization engine 104 instantiates and serves a virtual networkinterface card (VNIC) for each bare metal or virtual machine. Thevirtualization engine 104 can be the Network Encrypted Virtual Functions(NEVF). The network virtualization device 100 can be a physical card(e.g., a SmartNIC)) with dedicated resources attached to it (e.g.,memory and/or processors). In some embodiments, the networkvirtualization device 100 is a SmartTOR, a network appliance, or aservice host.

Routing and/or forwarding of packets within a cloud service providerinfrastructure can be performed by network virtualization devices. Anetwork virtualization device can implement one or more virtual networkfunctions, such as virtual network interface cards (VNIC), virtualrouters, virtual network gateways, and network encryption virtualfunctions. network virtualization devices are virtual objectsimplemented using software (e.g., code or instructions executed by aprocessor). A network virtualization devices is a hardware componentthat executes a virtual function such as a virtual router (e.g., avirtual router device is a physical device that executes codeimplementing a virtual router). For example, a VNIC is executed by aSmartNIC; the SmartNIC is a network virtualization device. In caseswhere a VNIC is executed by a host machine, the host machine is anetwork virtualization devices. In some embodiments, the virtual routeris executed by a top-of-rack (TOR) switch (and the TOR is the virtualrouter device). A SmartNIC is just one example of a networkvirtualization devices.

A virtual machine 108 is a program on a computer that performs like aseparate computer inside the computer. Virtual machines can be createdusing virtualization software. The virtual machine 108 can executevarious virtual functions.

The virtualization engine 104 comprises a memory device 112 and a cryptoprocessor 116. Memory device 112 is configured to store a key, such as acrypto key. In some embodiments, the memory device 112 is a staticrandom access memory (SRAM) device comprising a capacitor and atransistor.

The crypto processor 116 is configured to encrypt and/or decrypt data toand from the virtual machine 108 using the key stored in the memorydevice 112. A transmit packet TX is a data packet sent from the virtualmachine 108. A receive packet RX is a data packet sent to the virtualmachine 108. The transmit packet TX is encrypted by the crypto processor116. The receive packet RX is decrypted by the crypto processor 116. Thetransmit packet TX and/or the receive packet RX are encrypted/decryptedusing inline encryption/decryption. In some embodiments, thevirtualization engine 104 is configured to provide network routing ofdata packets (e.g., the virtualization engine 104 provides routing datafor the transmit packet TX).

In the embodiment shown, a virtualization engine 104 is configured toinstantiate only one virtual machine 108 at a time. This allowsdedicated encryption resources (e.g., the memory device 112 and/for thecrypto process or 116) per virtual machine 108, which can increasesecurity.

In the embodiment shown, the first virtualization engine 104-1 comprisesa first memory device 112-1 and a first crypto processor 116-1; and thesecond virtualization engine 104-2 comprises a second memory device112-2 and a second crypto processor 116-2. Accordingly, the firstvirtualization engine 104-1 in the second virtualization engine 104-2are part of the same device. Though two virtualization engines 104 areshown to be part of the network virtualization device 100, it is to beunderstood that more than two virtualization engines 104 could be partof the network virtualization device 100 (e.g., 3, 5, 10, 100, or morevirtualization engines 104 could be part of the network virtualizationdevice 100).

In some embodiments, the network virtualization device 100 is used toimplement virtual functions, such as VNIC, virtual router, and/or NEVFs.The network virtualization device 100 can be a card (e.g., a SmartNIC)in a server. Network virtualization device 100 is managed (e.g., ownedand/or operated) by a host for one or more clients to set up one or moreVCNs. The host is the administrator of the network virtualization device100. A key can be stored in the memory device 112 (e.g., encrypted) sothe host (e.g., administrator) does not have access to the key stored inthe memory device 112. By the host not having access to the key, aclient can be assured of data security, even if security of the host iscompromised.

An Ethernet bridge 120 allows the first virtualization engine 104-1 tocommunicate via the Internet and/or to communicate with the secondvirtualization engine 104-2 (e.g., when the first virtual machine 108-1and the second virtual machine 108-2 are part of the same virtual cloudnetwork). A hypervisor 124 is used by the host to share resources of acomputing system between virtual machines 108.

FIG. 2 is a depiction of one embodiment of multiple virtualizationengines 104 receiving crypto keys 204 from a key management service 208.In the embodiment shown, there are three virtualization engines 104.Though three virtualization engines 104 are shown, more or lessvirtualization engines 104 can be used. The virtualization engines 104each instantiate one (and in some embodiments only one) virtual machine108. The virtual machines 108 in FIG. 2 are part of a common virtualcloud network (VCN) 212. Since the virtualization engines 104 are partof the same VCN 212, the virtualization engines 104 each receive thesame key (e.g., the same crypto key 204), which enables thevirtualization engines 104 to securely communicate with each other(e.g., using the Ethernet bridge 120 shown in FIG. 1 ) using encrypteddata. Accordingly, the first virtualization engine 104-1 is configuredto receive the crypto key 204 from the key management service 208. Thefirst virtualization engine 104-1 saves the crypto key 204 in the firstmemory device 112-1.

A VCN control plane 216 is configured to manage, monitor, and/or modifycloud infrastructure resources. The key management service 208 canprovide the crypto key 204 to the virtualization engine 104 for a clientwithout the host of the network virtualization device 100 having accessto the crypto key 204. By the host (e.g., a cloud service provider) nothaving access to the crypto key 204, the client controls the security ofthe VCN 212.

To get a key into the memory device 112 without the host having accessto the key, a customer can initialize a crypto key 204 in the keymanagement service 208 (e.g., OCI's Cloud Key Management Service) and/orgives permission to the virtualization engine 104 to access it. In acloud network, each resource can be assigned an identity principle(e.g., OCI's Cloud Identity Principle) whereby credentials can be givento each resource in order to authenticate a resource to other cloudresources. A virtualization engine 104 (e.g., an NEVF) is a resource andcan be assigned an identity principle. The virtualization engine 104 canbe authenticated to the key management service 208. The virtualizationengine 104 can request the customer key (e.g., the crypto key 204)

The virtualization engine 104 can request the crypto key 204 from thekey management service 208 (e.g., using the identity principle toauthenticate itself to request the key). The key management system 208can push a key (and/or updates) to the virtualization engine 104 (e.g.,after authenticating the virtualization engine (104). Requesting orpushing keys is done without the host of the cloud network provisioningthe key to the virtualization engine 104 (e.g., into SRAM of thevirtualization engine 104). A security protocol can be pre-sharedbetween the key management system 208 and virtualization engine 104 sothat the key management system can route data to the virtualizationengine 104 with a pre-shared secret to initialize the key in memory ofthe virtualization engine 104.

The same crypto key 204 is distributed to each virtualization engine 104supporting a virtual machine 108 in the virtual cloud network 212. Thecrypto key 204 can be distributed to the virtual engine 104 when thevirtual machine 108 is instantiated. For example, a customer can beasked if the VCN 212 is to be encrypted when the customer creates theVCN 212 (e.g., the customer can check a box for encryption of the VCN212). When an instance of a virtual machine 108 is launched, anunderlying protocol goes from the key management service 208 to thevirtual engine 104 to distribute the crypto key 204 to the memory device112 of the virtual engine 104. Crypto keys 204 can be updatedperiodically (e.g., hourly, daily, weekly, etc.) and/or updated by thecustomer (e.g., customer selects or defines an update schedule and/orselects to update the crypto key 204 immediately). In some embodiments,the customer generates multiple keys and, when it is time to rotate to anew key (e.g., every day at time T), the crypto key 204 is updated(e.g., each virtual engine 104 reaches out to the key management service208 at time T). The new key is published in the memory device 112. Keysynchronization (e.g., auto synchronization) can be used for multiplehosts (e.g., a synchronization counter for each virtualization engine104 could be used to publish a new key in the memory device 112). Insome embodiments, the crypto key 204 is rotated on each virtualizationengine 104 based on some encryption scheme (e.g., the crypto key 204 isrefreshed). Thus the crypto key 204 can be pushed and/or refreshedconcurrently to or on each virtualization engine 104 that is part of theVCN 212. The key management service 208 can have a single encryptionrelationship with the VCN 212, so the key management service 208 doesnot have to maintain relationships with different devices.

By encrypting data, wherein the customer controls the keys, customerscan be assured data is encrypted on a host's wires. In some embodiments,customers can communicate with a host using a transport layer security(TLS) tunnel. However, TLS has bugs and can have security problems. Byallowing customers to control keys using the key management service 208,bugs and security problems of TLS can be avoided or decreased. In someembodiments, a TLS tunnel or a custom security protocol based onpre-shared keys can be used for secure communication between an NEVF anda key management service.

Though the description shows crypto keys 204 being distributed andmanaged at the VCN 212 level, similar processes and techniques can beused at other levels, such as at a subnet level. For example, encryptionkeys can be used at L2 or L3 of a VCN 212.

FIG. 3 is a depiction of one embodiment of a network virtualizationdevice 100 supporting multiple clients with different crypto keys 304.The network virtualization device 100 comprises a first virtualizationengine 104-1, a second virtualization engine 104-2, a thirdvirtualization engine 104-3, and a fourth virtualization engine 104-4.The first virtualization engine 104-1 is configured to instantiate afirst virtual machine 108-1. The second virtualization engine 104-2 isconfigured to instantiate a second virtual machine 108-2. The thirdvirtualization engine 104-3 is configured to instantiate a third virtualmachine 108-3. The fourth virtualization engine 104-4 is configured toinstantiate a fourth virtual machine 108-4.

The first virtual machine 108-1 and the third virtual machine 108-3 arepart of a first VCN 312-1. The second virtual machine 108-2 and thefourth virtual machine 108-4 are part of a second VCN 312-2. The firstVCN 312-1 is for a first client. The second VCN 312-2 is for a secondclient, wherein the second client is not the same as the first client.Thus multiple NEVFs on one device can be used to support virtualmachines belonging to different virtual cloud networks.

The first virtualization engine 104-1 and the third virtualizationengine 104-3 receive a first crypto key 304-1 from a first keymanagement service 208-1. The second virtualization engine 104-2 and thefourth virtualization engine 104-4 receive a second crypto key 304-2from a second key management service 208-2. The second crypto key 304-2is different than the first crypto key 304-1. In some embodiments,virtualization engines 104 of the second VCN 312-2 receive the secondcrypto key 304-2 from the same key management service as virtualizationengines 104 of the first VCN 312-1 (e.g., virtualization engines 104 ofthe second VCN 312-2 receive the second crypto key 304-2 from the firstkey management service 208-1).

The first virtual engine 104-1 stores the first crypto key 304-1 in thefirst memory device 112-1. The second virtual engine 104-2 stores asecond crypto key 304-2 in the second memory device 112-2. Similarly,the third virtualization engine 104-3 and the fourth virtualizationengine 104-4 each store a respective crypto key 304 in a memory device112. The host of the network virtualization device 100 does not haveaccess to the first crypto key 304-1 or the second crypto key 304-2. Byhaving one virtualization engine 104 per virtual machine 108 (e.g., byhaving dedicated resources, such as one memory device 112 per virtualmachine 108) enables one network virtualization device 100 to securelysupport multiple VCNs 312 for multiple customers. Since each customermanages their own crypto key 304 for a VCN 312, each customer's data canbe managed securely. Further, a data compromise of the host would notlead to a data compromise of the VCNs 312, thereby providing additionalsecurity confidence to customers.

FIG. 4 is a flowchart illustrating one embodiment of a process 400 forencrypting data in a virtual cloud network. Process 400 begins in step402 with instantiating a first virtual machine. For example, the firstvirtualization engine 104-1 instantiates a first virtual machine 108-1as shown in FIG. 1 . In step 404, a second virtual machine isinstantiated. For example, the second virtualization engine 104-2instantiates the second virtual machine 108-2 in FIG. 1 . Thevirtualization engine 104 comprises a memory device 112 and a cryptoprocessor 116, as shown in FIG. 1 .

A first key is stored in a first memory device, step 406. For example,crypto key 204 is stored in the first memory device 112-1 of the firstvirtualization engine 104-1, as shown in FIG. 2 . The first key can beretrieved from (e.g., requested from or pushed by) a key managementservice. In some embodiments, a customer of a virtual cloud network hascontrol over the first key so the host of the first virtualizationengine 104-1 does not have access to the key.

A second key is stored in a second memory device, step 408. For example,crypto key 204 is stored in the second memory device 112-2 of the secondvirtualization engine 104-2, as shown in FIG. 2 . The second key can beretrieved from (e.g., requested from or pushed by) the key managementservice. In some embodiments, a customer of a virtual cloud network hascontrol over the second key so the host of the virtualization engine 104does not have access to the second key. The second key can be the sameas the first key as shown in FIG. 2 . The second key can be differentthan the first key, as shown in FIG. 3 . For example, the second keycould be different from the first key because the second virtual machineis part of a different virtual cloud network than the first virtualmachine.

In step 410, data for the first virtual machine is encrypted using thefirst key. For example, the first crypto processor 116-1 encryptstransmit data TX from the first virtual machine 108-1 in FIG. 1 . Instep 412, data for the second virtual machine is encrypted using thesecond key. For example, the second crypto processor 116-2 encryptstransmit data TX from the second virtual machine 108-2 in FIG. 1 . Ifthe first virtual machine 108-1 and the second virtual machine 108-2 arepart of the same virtual cloud network, then the first virtual machine108-1 can transmit and/or and receive data, securely, from into thesecond virtual machine 108-2 using the same key (e.g., see FIG. 2 ).However, if the first key is different from the second key, as shown inFIG. 3 , than the first virtual machine 108-1 does not send and/orreceive encrypted data from the second virtual machine 108-2 (unlessthere was some sort of additional arrangement between the first VCN312-1 and the second VCN 312-2 in FIG. 3 ).

The first virtualization engine 104-1 and the second virtualizationengine 104-2 are on the same device (e.g., part of the same card in aserver). Since the virtualization engine 104 is used to instantiate onlyone virtual machine, and/or since the virtualization engine has one ormore dedicated resources, data to and from each virtual machine can besecurely encrypted and/or decrypted without a host of the networkvirtualization device having access to the first key or the second key.

FIG. 5 is a flowchart illustrating one embodiment of a process 500 forusing multiple crypto keys for data encryption for multiple virtualcloud networks. Process 500 begins in step 502 with instantiating afirst set of virtual machines for a first customer. A first set ofvirtual engines are used to instantiate the first set of virtualmachines. The first set of virtual machines are part of a first virtualcloud network. In this embodiment, a set comprises two or more. Forexample, the first virtualization engine 104-1 and the thirdvirtualization engine 104-3 are used to instantiate the first virtualmachine 108-1 and the third virtual machine 108-3 in FIG. 3 ; the firstvirtual machine 108-1 and the third virtual machine 108-3 are part ofthe first virtual cloud network 312-1.

A second set of virtual machines are instantiated for a second customer,step 504. A second set of virtual engines are used to instantiate thesecond set of virtual machines. The second set of virtual machines arepart of a second virtual cloud network. For example, the secondvirtualization engine 104-2 and the fourth virtualization engine 104-4are used to instantiate the second virtual machine 108-2 and the fourthvirtual machine 108-4 in FIG. 3 ; the second virtual machine 108-2 andthe fourth virtual machine 108-4 are part of the second virtual cloudnetwork 312-2.

In step 506 the first key, e.g., first crypto key 304-1 in FIG. 3 , isreceived by the virtualization engines used to instantiate the virtualmachines of the first virtual cloud network. A second key, e.g., thesecond crypto key 304-2 in FIG. 3 , is received by the virtualizationengines used to instantiate the virtual machines of the second virtualcloud network, step 508. The first key can be received from a first keymanagement service and the second key can be received from a second keymanagement service, different from the first key management service.

The first key is used to encrypt data for the first customer, step 510.The second key is used to encrypt data for the second customer, step512. The host does not have access to the first key and/or the secondkey.

FIG. 6 is a depiction of one embodiment of a virtual cloud network 312receiving data through a VPN (Virtual Private Network) gateway 604. Datais encrypted on a customer headend 608 (e.g., a VPN headend). A headendis a device used as a termination for a secured transmission link. Thecustomer headend 608 is part of a customer on-premise network 612. Datais transmitted from the customer headend 608 to the VPN gateway 604(e.g., through an Inet gateway 616). The VPN gateway is owned and/oroperated by a host of the VCN 312. An Internet Protocol SECurity (IPSec)tunnel can be formed from the customer headend 608 to the VPN gateway604, so that data packets are encrypted at the customer headend 608 anddecrypted at the VPN gateway 604; and vice versa for encrypted data sentfrom the VPN Gateway 604 to the customer headend 608. Data sent from thecustomer headend 608 to the VPN gateway 604 can be sent over publiclinks (e.g., the Internet) or private links (e.g., using OracleFastConnect). The IPSec tunnel can use layer 1 and/or layer 2encryption.

At the VPN gateway 604, the host can receive data from one or morecustomers. In some embodiments, the VPN gateway 604 can be a dedicatedbare-metal host for a single customer or a multi-tenant host withnetwork hardware with multiple NEVFs terminating VPN connections frommultiple customers. The redirector 620 is used to route data from afirst customer to a first network virtualization device 624-1, and toroute data from a second customer to a second network virtualizationdevice 624-2. The first network virtualization device 624-1 encryptsdata of the first customer for a first virtual cloud network 312-1. Thesecond network virtualization device 624-2 encrypts data of the secondcustomer for a second virtual cloud network 312-2.

Unencrypted data is sent from the VPN gateway 604 to a redirector 620.The network virtualization device 624 is configured to encrypt data fora virtual cloud network 312. For example, the network virtualizationdevice 624 is a virtualization engine 104 as shown in FIG. 2 .

The virtual engine 104 can receive a crypto key 204 from the keymanagement service 208, as shown in FIG. 2 , so that data within avirtual cloud network 312 can be encrypted using a crypto key 204provisioned by the customer.

A customer on-premise network 612 comprises devices owned and/ormaintained by the host. For example, the customer headend 608 is anetwork card in a machine owned and/or maintained by the customer. Insome embodiments, the customer headend 608 is separated from the VPNgateway 604 (e.g., a network card owned and/or maintained by the host)by 5, 10, 20, 50, 100, 500 or more kilometers.

The VPN gateway 604, the redirector 620, and the network virtualizationdevices 624 are part of a cloud service provider infrastructure (CSPI)628. The host owns and/or maintains the CSPI 628. Accordingly, the hostmanages data security, if any, from the VPN gateway 604 to the networkvirtualization device 624. Additionally, for the IPSec tunnel to beestablished from the customer headend 608 to the VPN gateway 604, thecustomer and the host share a key (e.g., for symmetric encryption)and/or keys (e.g., for asymmetric encryption). For example, the hostcould give a customer a key for establishing the IPSec tunnel, thecustomer could provide the host the key, or the customer and host couldagree on an encryption scheme.

FIG. 7 is a depiction of one embodiment of a virtual cloud networkreceiving data through a Virtual Cloud Network (VCN) headend 704. Insome situations, a customer might desire to reach a virtual cloudnetwork 312 securely from the customer on-premise network 612, withoutthe host having access to the data and/or keys used for encryption. Forexample, the VPN gateway 604 uses an encryption key that the host hasaccess to, in order to decrypt data from the customer headend 608.Further, a customer might desire to not have its data transmittedunencrypted between machines of the host. For example, data is notencrypted through the redirector 620 in FIG. 6 .

A VCN headend 704 is used to enable a customer to reach a VCN securelyfrom their own on-premise network (referred to as end-to-end encryptionin this disclosure) and/or allow the customer to control/manage theencryption key(s). The VCN headend 704 is a network resource dedicatedto a specific customer (e.g., the host provides electricity and/orcooling, but the host cannot log into the VCN headend 704). In someembodiments, the VCN headend 704 is or can include a SmartNIC or othernetwork virtualization device such as one or several NICs, SmartToRs, orthe like. A SmartNIC can be an application-specific integrated circuit(ASIC), a field programmable gate array (FPGA), or a system on a chip(SoC). The VCN headend 704 can comprise one or more processors and oneor more memory devices.

Data is encrypted from the customer headend 608 to the VCN headend 704using an encryption key 708. The VCN headend 704 can be configured toreceive encrypted data over public links (e.g., the public Internet)and/or over private links (e.g., Oracle FastConnect). For example, a VPNtunnel is formed from the customer headend 608 to the VCN headend 704,and the customer headend 608 and the VCN headend 704 are terminationpoints of the VPN tunnel. So instead of terminating the VPN tunnel atthe VPN gateway 604 as shown in FIG. 6 , the VPN tunnel terminates atthe VCN headend 704 (e.g., bypassing the VPN gateway 604 and/orbypassing the redirector 620).

Since the VCN headend 704 is a resource dedicated to the customer, thecustomer can provision the encryption key 708 securely in a memorydevice of the VCN headend 704. For example, the customer could log intothe VCN headend 704 to provision the encryption key 708, and/or thecustomer could use the key management service 208 in FIG. 2 to provisionthe encryption key 708, similar to using the key management service 208to provision the crypto key 304 to a virtualization device 104. Forexample, the key management service 208 could provide the encryption key708 to the VCN headend 704 after confirming (e.g., authenticating) theVCN headend 704 has proper permission or credentials to receive theencryption key 708.

The VCN headend 704, in certain embodiments, is a physical device thatdoes not provide a virtual function. Decrypted data is sent from the VCNheadend 704 to the network virtualization device 624. In the embodimentshown, the VCN headend 704 and the network virtualization device 624 arepart of a VCN gateway 712. For example, the VCN gateway 712 is aphysical host with two network cards, one network card for the VCNheadend 704 and a second network card for the network virtualizationdevice 624. The VCN gateway 712 can be dedicated to a customer such thatno other customers of the host use the VCN gateway 712. In an example,the VCN headend 704 and the network virtualization device 624 are partof the same server to increase security while unencrypted data is beingtransmitted from the VCN headend 704 to the network virtualizationdevice 624. In some embodiments, the VCN headend 704 is on the sameboard (e.g., network card), on a same rack, and/or in a same room as thenetwork virtualization device 624 (e.g., for security). The VCN headend704 and the network virtualization device 624 can be part of ahigh-performance NIC to handle traffic as needed. The VCN gateway 712has the ability to terminate an IPSec tunnel and also has an NEVF toprovision the crypto key to encrypt traffic and send it into a virtualcloud network. The VCN gateway 712 allows the customer to control/manageboth the crypto key 304 and the encryption key 708. Though the VCNgateway 712 is part of the cloud service provider infrastructure(infrastructure of the host), the host does not manage or have access tothe encryption key 708.

The network virtualization device 624 is used to encrypt data (e.g.,using a network encryption virtual function) for the virtual cloudnetwork 312. For example, the network virtualization device 624 is avirtualization engine 104 as described in FIGS. 1-3 and uses the cryptokey 304 to encrypt data for the virtual cloud network 312. Thus, thenetwork virtualization device 624 can provide an instance of a virtualmachine in the virtual cloud network 312.

In some embodiments, the network virtualization device 624 is part ofthe VCN headend 704, allowing the VPN tunnel to be terminated at aninstance of the virtual cloud network 312. The VCN gateway 712 can beused to decrypt data using the encryption key 708 and encrypt data usingthe crypto key 304.

In some configurations, one customer can have two or more VCN headends704. For example, a customer with high volume might have multiple VCNheadends 704 for increased bandwidth for securely uploading and/ordownloading data to one or more virtual cloud networks 312. Oneencryption key 708 could be used for multiple VCN headends 704supporting one customer, or different encryption keys 708 could be usedfor different VCN headends 704. With the customer provisioning theencryption key(s) 708, the customer could decide whether to have oneencryption key 708 or multiple encryption keys 708. In some embodiments,one NIC is used for multiple VCN headends 704.

In some configurations, the encryption key 708 is a long-lived key(e.g., rotated or changed on a weekly, monthly, or manual basis). Thecrypto key 304 could be a short-lived key (e.g., rotated or changed lessthan weekly or daily, such as every 4, 8, 12, 24, or 36 hours). Thus theencryption key 708 can be configured to be changed less frequently thanthe crypto key 304.

A system can comprise a network headend device (e.g., the VCN headend704). The network headend device can be configured to receive a firstkey (e.g., the encryption key 708) provisioned by the customer (e.g.,the customer can log into the VCN headend 704 to provision the first keyand/or use a key management service). The network headend device isconfigured to receive a first data packet from a device of a customer.For example, the network headend device is configured to receive datafrom the customer headend 608. The network headend device is configuredto decrypt the first data packet using the first key to obtaininformation. The information is at least a portion of the decrypteddata. A network virtualization device (e.g., network virtualizationdevice 624) is configured to receive the information from the networkheadend device, after the first data packet is decrypted; ascertain thatthe information is to be sent to a virtual machine in a virtual cloudnetwork (e.g., a virtual machine in the virtual cloud network 312); andencrypt the information with a second key to generate a second datapacket. For example, the information is encrypted using the crypto key304. The second data packet is routed to the virtual machine (e.g., to anetwork virtualization device used to instantiate the virtual machine).

FIG. 8 is a depiction of an embodiment of one VCN gateway 712 supportingmore than one virtual cloud networks 312 for a customer. Data from acustomer headend 608 is securely transmitted to a VCN headend 704 usingthe encryption key 708. The VCN headend 704 is part of the VCN gateway712. The VCN gateway comprises a first network virtualization device624-1 and a second network virtualization device 624-2. Though twonetwork virtualization devices 624, and two virtual cloud networks 312,are shown, more than two can be used (e.g., 3, 4, 5, 10, 20, or more).As mentioned in conjunction with FIG. 7 , more than one VCN headend 704could also be used (e.g., 2, 3, 4, or more).

After decrypting data received from the customer headend 608, the VCNheadend 704 determines if the data is intended for the first virtualcloud network 312-1, the second virtual cloud network 312-2, or both thefirst virtual could network 312-1 and the second virtual cloud network312-2. For data intended for the first virtual cloud network 312-1, thedata is re-encrypted using the first crypto key 304-1 using the firstnetwork virtualization device 624-1, and sent to the first virtualnetwork 312-1; for data intended for the second virtual cloud network312-2, data is re-encrypted using the second crypto key 304-2 using thesecond network virtualization device 624-2, and sent to the secondvirtual cloud network 312-2. Thus one VCN headend 704 can be used tosupport multiple virtual cloud networks 312 for a customer. In someembodiments, one NIC is used for a plurality of network virtualizationdevices 624. In some embodiments, the plurality of networkvirtualization devices 624 are part of the same NIC as the VCN headend704. In other embodiments, the VCN headend 704 is on a different NICthan the network virtualization device 624.

FIG. 9 is a flowchart illustrating one embodiment of a process 900 forend-to-end encryption for a virtual cloud network. Process 900 begins instep 902 with receiving a first key in a network headend device. Forexample, the encryption key 708 shown in FIG. 7 is the first key, andthe VCN headend 704 is the network headend device. The first key can beprovisioned by a customer (e.g., so that the first key is managed by thecustomer, without the host knowing what the first key is). In step 904,the network headend device receives a first data packet. For example,the VCN headend 704 receives encrypted data from a device of thecustomer (e.g., from the customer headend 608). The network headenddevice decrypts the first data packet to obtain information, step 906.The information is at least a portion of the decrypted first datapacket. In some embodiments, a gateway (e.g., VPN gateway 604 in FIG. 6) can terminate a VPN tunnel from the customer headend 608 using thefirst key, and re-encrypt traffic with a second key to send packets toinstances (e.g., VMs/BMs) in a VCN, where the second key is the VCNencryption key.

The network headend device transmits the information to a networkvirtualization device, so that the network virtualization devicereceives the information from the network headend device, step 908. Forexample, the VCN headend 704 transmits decrypted data to the networkvirtualization device 624 in FIG. 7 . In some embodiments, the networkvirtualization device 624 can be an integral component of the VCNheadend 704. In step 910, the network virtualization device encrypts theinformation using a second key to generate a second data packet. Forexample, the network virtualization device 624 uses the crypto key 304to encrypt data for the virtual cloud network 312. The second datapacket is then routed to a virtual machine in the virtual cloud network.For example, encrypted data is sent by the network virtualization device624 to the virtual cloud network 312 in FIG. 7 .

In some configurations, data from the customer headend 608 to the VCNheadend 704 in FIG. 7 is encrypted, or data from the networkvirtualization device 624 to the virtual cloud network 312 is encrypted,but not both. In some embodiments, the network virtualization device 624ascertains that data in the virtual cloud network is to be encryptedbefore encrypting the information received from the VCN headend 704.

Infrastructure as a service (IaaS) is one particular type of cloudcomputing. IaaS can be configured to provide virtualized computingresources over a public network (e.g., the Internet). In an IaaS model,a cloud computing provider can host the infrastructure components (e.g.,servers, storage devices, network nodes (e.g., hardware), deploymentsoftware, platform virtualization (e.g., a hypervisor layer), or thelike). In some cases, an IaaS provider may also supply a variety ofservices to accompany those infrastructure components (e.g., billing,monitoring, logging, security, load balancing and clustering, etc.).Thus, as these services may be policy-driven, IaaS users may be able toimplement policies to drive load balancing to maintain applicationavailability and performance.

In some instances, IaaS customers may access resources and servicesthrough a wide area network (WAN), such as the Internet, and can use thecloud provider's services to install the remaining elements of anapplication stack. For example, the user can log in to the IaaS platformto create virtual machines (VMs), install operating systems (OSs) oneach VM, deploy middleware such as databases, create storage buckets forworkloads and backups, and even install enterprise software into thatVM. Customers can then use the provider's services to perform variousfunctions, including balancing network traffic, troubleshootingapplication issues, monitoring performance, managing disaster recovery,etc.

In most cases, a cloud computing model will use the participation of acloud provider. The cloud provider may, but need not be, a third-partyservice that specializes in providing (e.g., offering, renting, selling)IaaS. An entity might also opt to deploy a private cloud, becoming itsown provider of infrastructure services.

In some examples, IaaS deployment is the process of putting a newapplication, or a new version of an application, onto a preparedapplication server or the like. It may also include the process ofpreparing the server (e.g., installing libraries, daemons, etc.). Thisis often managed by the cloud provider, below the hypervisor layer(e.g., the servers, storage, network hardware, and virtualization).Thus, the customer may be responsible for handling (OS), middleware,and/or application deployment (e.g., on self-service virtual machines(e.g., that can be spun up on demand) or the like.

In some examples, IaaS provisioning may refer to acquiring computers orvirtual hosts for use, and even installing needed libraries or serviceson them. In most cases, deployment does not include provisioning, andthe provisioning may need to be performed first.

In some cases, there are two different problems for IaaS provisioning.First, there is the initial challenge of provisioning the initial set ofinfrastructure before anything is running. Second, there is thechallenge of evolving the existing infrastructure (e.g., adding newservices, changing services, removing services, etc.) once everythinghas been provisioned. In some cases, these two challenges may beaddressed by enabling the configuration of the infrastructure to bedefined declaratively. In other words, the infrastructure (e.g., whatcomponents are needed and how they interact) can be defined by one ormore configuration files. Thus, the overall topology of theinfrastructure (e.g., what resources depend on which, and how they eachwork together) can be described declaratively. In some instances, oncethe topology is defined, a workflow can be generated that creates and/ormanages the different components described in the configuration files.

In some examples, an infrastructure may have many interconnectedelements. For example, there may be one or more virtual private clouds(VPCs) (e.g., a potentially on-demand pool of configurable and/or sharedcomputing resources), also known as a core network. In some examples,there may also be one or more security group rules provisioned to definehow the security of the network will be set up and one or more virtualmachines (VMs). Other infrastructure elements may also be provisioned,such as a load balancer, a database, or the like. As more and moreinfrastructure elements are desired and/or added, the infrastructure mayincrementally evolve.

In some instances, continuous deployment techniques may be employed toenable deployment of infrastructure code across various virtualcomputing environments. Additionally, the described techniques canenable infrastructure management within these environments. In someexamples, service teams can write code that is desired to be deployed toone or more, but often many, different production environments (e.g.,across various different geographic locations, sometimes spanning theentire world). However, in some examples, the infrastructure on whichthe code will be deployed must first be set up. In some instances, theprovisioning can be done manually, a provisioning tool may be utilizedto provision the resources, and/or deployment tools may be utilized todeploy the code once the infrastructure is provisioned.

FIG. 10 is a block diagram 1000 illustrating an example pattern of anIaaS architecture, according to at least one embodiment. Serviceoperators 1002 can be communicatively coupled to a secure host tenancy1004 that can include a virtual cloud network (VCN) 1006 and a securehost subnet 1008. In some examples, the service operators 1002 may beusing one or more client computing devices, which may be portablehandheld devices (e.g., an iPhone®, cellular telephone, an iPad®,computing tablet, a personal digital assistant (PDA)) or wearabledevices (e.g., a Google Glass® head mounted display), running softwaresuch as Microsoft Windows Mobile®, and/or a variety of mobile operatingsystems such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, andthe like, and being Internet, e-mail, short message service (SMS),Blackberry®, or other communication protocol enabled. Alternatively, theclient computing devices can be general purpose personal computersincluding, by way of example, personal computers and/or laptop computersrunning various versions of Microsoft Windows®, Apple Macintosh®, and/orLinux operating systems. The client computing devices can be workstationcomputers running any of a variety of commercially-available UNIX® orUNIX-like operating systems, including without limitation the variety ofGNU/Linux operating systems, such as for example, Google Chrome OS.Alternatively, or in addition, client computing devices may be any otherelectronic device, such as a thin-client computer, an Internet-enabledgaming system (e.g., a Microsoft Xbox gaming console with or without aKinect® gesture input device), and/or a personal messaging device,capable of communicating over a network that can access the VCN 1006and/or the Internet.

The VCN 1006 can include a local peering gateway (LPG) 1010 that can becommunicatively coupled to a secure shell (SSH) VCN 1012 via an LPG 1010contained in the SSH VCN 1012. The SSH VCN 1012 can include an SSHsubnet 1014, and the SSH VCN 1012 can be communicatively coupled to acontrol plane VCN 1016 via the LPG 1010 contained in the control planeVCN 1016. Also, the SSH VCN 1012 can be communicatively coupled to adata plane VCN 1018 via an LPG 1010. The control plane VCN 1016 and thedata plane VCN 1018 can be contained in a service tenancy 1019 that canbe owned and/or operated by the IaaS provider.

The control plane VCN 1016 can include a control plane demilitarizedzone (DMZ) tier 1020 that acts as a perimeter network (e.g., portions ofa corporate network between the corporate intranet and externalnetworks). The DMZ-based servers may have restricted responsibilitiesand help keep security breaches contained. Additionally, the DMZ tier1020 can include one or more load balancer (LB) subnet(s) 1022, acontrol plane app tier 1024 that can include app subnet(s) 1026, acontrol plane data tier 1028 that can include database (DB) subnet(s)1030 (e.g., frontend DB subnet(s) and/or backend DB subnet(s)). The LBsubnet(s) 1022 contained in the control plane DMZ tier 1020 can becommunicatively coupled to the app subnet(s) 1026 contained in thecontrol plane app tier 1024 and an Internet gateway 1034 that can becontained in the control plane VCN 1016, and the app subnet(s) 1026 canbe communicatively coupled to the DB subnet(s) 1030 contained in thecontrol plane data tier 1028 and a service gateway 1036 and a networkaddress translation (NAT) gateway 1038. The control plane VCN 1016 caninclude the service gateway 1036 and the NAT gateway 1038.

The control plane VCN 1016 can include a data plane mirror app tier 1040that can include app subnet(s) 1026. The app subnet(s) 1026 contained inthe data plane mirror app tier 1040 can include a virtual networkinterface controller (VNIC) 1042 that can execute a compute instance1044. The compute instance 1044 can communicatively couple the appsubnet(s) 1026 of the data plane mirror app tier 1040 to app subnet(s)1026 that can be contained in a data plane app tier 1046.

The data plane VCN 1018 can include the data plane app tier 1046, a dataplane DMZ tier 1048, and a data plane data tier 1050. The data plane DMZtier 1048 can include LB subnet(s) 1022 that can be communicativelycoupled to the app subnet(s) 1026 of the data plane app tier 1046 andthe Internet gateway 1034 of the data plane VCN 1018. The app subnet(s)1026 can be communicatively coupled to the service gateway 1036 of thedata plane VCN 1018 and the NAT gateway 1038 of the data plane VCN 1018.The data plane data tier 1050 can also include the DB subnet(s) 1030that can be communicatively coupled to the app subnet(s) 1026 of thedata plane app tier 1046.

The Internet gateway 1034 of the control plane VCN 1016 and of the dataplane VCN 1018 can be communicatively coupled to a metadata managementservice 1052 that can be communicatively coupled to public Internet1054. Public Internet 1054 can be communicatively coupled to the NATgateway 1038 of the control plane VCN 1016 and of the data plane VCN1018. The service gateway 1036 of the control plane VCN 1016 and of thedata plane VCN 1018 can be communicatively couple to cloud services1056.

In some examples, the service gateway 1036 of the control plane VCN 1016or of the data plan VCN 1018 can make application programming interface(API) calls to cloud services 1056 without going through public Internet1054. The API calls to cloud services 1056 from the service gateway 1036can be one-way: the service gateway 1036 can make API calls to cloudservices 1056, and cloud services 1056 can send requested data to theservice gateway 1036. But, cloud services 1056 may not initiate APIcalls to the service gateway 1036.

In some examples, the secure host tenancy 1004 can be directly connectedto the service tenancy 1019, which may be otherwise isolated. The securehost subnet 1008 can communicate with the SSH subnet 1014 through an LPG1010 that may enable two-way communication over an otherwise isolatedsystem. Connecting the secure host subnet 1008 to the SSH subnet 1014may give the secure host subnet 1008 access to other entities within theservice tenancy 1019.

The control plane VCN 1016 may allow users of the service tenancy 1019to set up or otherwise provision desired resources. Desired resourcesprovisioned in the control plane VCN 1016 may be deployed or otherwiseused in the data plane VCN 1018. In some examples, the control plane VCN1016 can be isolated from the data plane VCN 1018, and the data planemirror app tier 1040 of the control plane VCN 1016 can communicate withthe data plane app tier 1046 of the data plane VCN 1018 via VNICs 1042that can be contained in the data plane mirror app tier 1040 and thedata plane app tier 1046.

In some examples, users of the system, or customers, can make requests,for example create, read, update, or delete (CRUD) operations, throughpublic Internet 1054 that can communicate the requests to the metadatamanagement service 1052. The metadata management service 1052 cancommunicate the request to the control plane VCN 1016 through theInternet gateway 1034. The request can be received by the LB subnet(s)1022 contained in the control plane DMZ tier 1020. The LB subnet(s) 1022may determine that the request is valid, and in response to thisdetermination, the LB subnet(s) 1022 can transmit the request to appsubnet(s) 1026 contained in the control plane app tier 1024. If therequest is validated and requires a call to public Internet 1054, thecall to public Internet 1054 may be transmitted to the NAT gateway 1038that can make the call to public Internet 1054. Memory that may bedesired to be stored by the request can be stored in the DB subnet(s)1030.

In some examples, the data plane mirror app tier 1040 can facilitatedirect communication between the control plane VCN 1016 and the dataplane VCN 1018. For example, changes, updates, or other suitablemodifications to configuration may be desired to be applied to theresources contained in the data plane VCN 1018. Via a VNIC 1042, thecontrol plane VCN 1016 can directly communicate with, and can therebyexecute the changes, updates, or other suitable modifications toconfiguration to, resources contained in the data plane VCN 1018.

In some embodiments, the control plane VCN 1016 and the data plane VCN1018 can be contained in the service tenancy 1019. In this case, theuser, or the customer, of the system may not own or operate either thecontrol plane VCN 1016 or the data plane VCN 1018. Instead, the IaaSprovider may own or operate the control plane VCN 1016 and the dataplane VCN 1018, both of which may be contained in the service tenancy1019. This embodiment can enable isolation of networks that may preventusers or customers from interacting with other users', or othercustomers', resources. Also, this embodiment may allow users orcustomers of the system to store databases privately without needing torely on public Internet 1054, which may not have a desired level ofsecurity, for storage.

In other embodiments, the LB subnet(s) 1022 contained in the controlplane VCN 1016 can be configured to receive a signal from the servicegateway 1036. In this embodiment, the control plane VCN 1016 and thedata plane VCN 1018 may be configured to be called by a customer of theIaaS provider without calling public Internet 1054. Customers of theIaaS provider may desire this embodiment since database(s) that thecustomers use may be controlled by the IaaS provider and may be storedon the service tenancy 1019, which may be isolated from public Internet1054.

FIG. 11 is a block diagram 1100 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1102 (e.g. service operators 1002 of FIG. 10 ) can becommunicatively coupled to a secure host tenancy 1104 (e.g. the securehost tenancy 1004 of FIG. 10 ) that can include a virtual cloud network(VCN) 1106 (e.g. the VCN 1006 of FIG. 10 ) and a secure host subnet 1108(e.g. the secure host subnet 1008 of FIG. 10 ). The VCN 1106 can includea local peering gateway (LPG) 1110 (e.g. the LPG 1010 of FIG. 10) thatcan be communicatively coupled to a secure shell (SSH) VCN 1112 (e.g.the SSH VCN 1012 of FIG. 10 ) via an LPG 1010 contained in the SSH VCN1112. The SSH VCN 1112 can include an SSH subnet 1114 (e.g. the SSHsubnet 1014 of FIG. 10 ), and the SSH VCN 1112 can be communicativelycoupled to a control plane VCN 1116 (e.g. the control plane VCN 1016 ofFIG. 10 ) via an LPG 1110 contained in the control plane VCN 1116. Thecontrol plane VCN 1116 can be contained in a service tenancy 1119 (e.g.the service tenancy 1019 of FIG. 10 ), and the data plane VCN 1118 (e.g.the data plane VCN 1018 of FIG. 10 ) can be contained in a customertenancy 1121 that may be owned or operated by users, or customers, ofthe system.

The control plane VCN 1116 can include a control plane DMZ tier 1120(e.g. the control plane DMZ tier 1020 of FIG. 10 ) that can include LBsubnet(s) 1122 (e.g. LB subnet(s) 1022 of FIG. 10 ), a control plane apptier 1124 (e.g. the control plane app tier 1024 of FIG. 10 ) that caninclude app subnet(s) 1126 (e.g. app subnet(s) 1026 of FIG. 10 ), acontrol plane data tier 1128 (e.g. the control plane data tier 1028 ofFIG. 10 ) that can include database (DB) subnet(s) 1130 (e.g. similar toDB subnet(s) 1030 of FIG. 10 ). The LB subnet(s) 1122 contained in thecontrol plane DMZ tier 1120 can be communicatively coupled to the appsubnet(s) 1126 contained in the control plane app tier 1124 and anInternet gateway 1134 (e.g. the Internet gateway 1034 of FIG. 10 ) thatcan be contained in the control plane VCN 1116, and the app subnet(s)1126 can be communicatively coupled to the DB subnet(s) 1130 containedin the control plane data tier 1128 and a service gateway 1136 (e.g. theservice gateway of FIG. 10 ) and a network address translation (NAT)gateway 1138 (e.g. the NAT gateway 1038 of FIG. 10 ). The control planeVCN 1116 can include the service gateway 1136 and the NAT gateway 1138.

The control plane VCN 1116 can include a data plane mirror app tier 1140(e.g. the data plane mirror app tier 1040 of FIG. 10 ) that can includeapp subnet(s) 1126. The app subnet(s) 1126 contained in the data planemirror app tier 1140 can include a virtual network interface controller(VNIC) 1142 (e.g. the VNIC of 1042) that can execute a compute instance1144 (e.g. similar to the compute instance 1044 of FIG. 10 ). Thecompute instance 1144 can facilitate communication between the appsubnet(s) 1126 of the data plane mirror app tier 1140 and the appsubnet(s) 1126 that can be contained in a data plane app tier 1146 (e.g.the data plane app tier 1046 of FIG. 10 ) via the VNIC 1142 contained inthe data plane mirror app tier 1140 and the VNIC 1142 contained in thedata plan app tier 1146.

The Internet gateway 1134 contained in the control plane VCN 1116 can becommunicatively coupled to a metadata management service 1152 (e.g. themetadata management service 1052 of FIG. 10 ) that can becommunicatively coupled to public Internet 1154 (e.g. public Internet1054 of FIG. 10 ). Public Internet 1154 can be communicatively coupledto the NAT gateway 1138 contained in the control plane VCN 1116. Theservice gateway 1136 contained in the control plane VCN 1116 can becommunicatively couple to cloud services 1156 (e.g. cloud services 1056of FIG. 10 ).

In some examples, the data plane VCN 1118 can be contained in thecustomer tenancy 1121. In this case, the IaaS provider may provide thecontrol plane VCN 1116 for each customer, and the IaaS provider may, foreach customer, set up a unique compute instance 1144 that is containedin the service tenancy 1119. Each compute instance 1144 may allowcommunication between the control plane VCN 1116, contained in theservice tenancy 1119, and the data plane VCN 1118 that is contained inthe customer tenancy 1121. The compute instance 1144 may allowresources, that are provisioned in the control plane VCN 1116 that iscontained in the service tenancy 1119, to be deployed or otherwise usedin the data plane VCN 1118 that is contained in the customer tenancy1121.

In other examples, the customer of the IaaS provider may have databasesthat live in the customer tenancy 1121. In this example, the controlplane VCN 1116 can include the data plane mirror app tier 1140 that caninclude app subnet(s) 1126. The data plane mirror app tier 1140 canreside in the data plane VCN 1118, but the data plane mirror app tier1140 may not live in the data plane VCN 1118. That is, the data planemirror app tier 1140 may have access to the customer tenancy 1121, butthe data plane mirror app tier 1140 may not exist in the data plane VCN1118 or be owned or operated by the customer of the IaaS provider. Thedata plane mirror app tier 1140 may be configured to make calls to thedata plane VCN 1118 but may not be configured to make calls to anyentity contained in the control plane VCN 1116. The customer may desireto deploy or otherwise use resources in the data plane VCN 1118 that areprovisioned in the control plane VCN 1116, and the data plane mirror apptier 1140 can facilitate the desired deployment, or other usage ofresources, of the customer.

In some embodiments, the customer of the IaaS provider can apply filtersto the data plane VCN 1118. In this embodiment, the customer candetermine what the data plane VCN 1118 can access, and the customer mayrestrict access to public Internet 1154 from the data plane VCN 1118.The IaaS provider may not be able to apply filters or otherwise controlaccess of the data plane VCN 1118 to any outside networks or databases.Applying filters and controls by the customer onto the data plane VCN1118, contained in the customer tenancy 1121, can help isolate the dataplane VCN 1118 from other customers and from public Internet 1154.

In some embodiments, cloud services 1156 can be called by the servicegateway 1136 to access services that may not exist on public Internet1154, on the control plane VCN 1116, or on the data plane VCN 1118. Theconnection between cloud services 1156 and the control plane VCN 1116 orthe data plane VCN 1118 may not be live or continuous. Cloud services1156 may exist on a different network owned or operated by the IaaSprovider. Cloud services 1156 may be configured to receive calls fromthe service gateway 1136 and may be configured to not receive calls frompublic Internet 1154. Some cloud services 1156 may be isolated fromother cloud services 1156, and the control plane VCN 1116 may beisolated from cloud services 1156 that may not be in the same region asthe control plane VCN 1116. For example, the control plane VCN 1116 maybe located in “Region 1,” and cloud service “Deployment 10,” may belocated in Region 1 and in “Region 2.” If a call to Deployment 10 ismade by the service gateway 1136 contained in the control plane VCN 1116located in Region 1, the call may be transmitted to Deployment 10 inRegion 1. In this example, the control plane VCN 1116, or Deployment 10in Region 1, may not be communicatively coupled to, or otherwise incommunication with, Deployment 10 in Region 2.

FIG. 12 is a block diagram 1200 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1202 (e.g. service operators 1002 of FIG. 10 ) can becommunicatively coupled to a secure host tenancy 1204 (e.g. the securehost tenancy 1004 of FIG. 10 ) that can include a virtual cloud network(VCN) 1206 (e.g. the VCN 1006 of FIG. 10 ) and a secure host subnet 1208(e.g. the secure host subnet 1008 of FIG. 10 ). The VCN 1206 can includean LPG 1210 (e.g. the LPG 1010 of FIG. 10 ) that can be communicativelycoupled to an SSH VCN 1212 (e.g. the SSH VCN 1012 of FIG. 10 ) via anLPG 1210 contained in the SSH VCN 1212. The SSH VCN 1212 can include anSSH subnet 1214 (e.g. the SSH subnet 1014 of FIG. 10 ), and the SSH VCN1212 can be communicatively coupled to a control plane VCN 1216 (e.g.the control plane VCN 1016 of FIG. 10 ) via an LPG 1210 contained in thecontrol plane VCN 1216 and to a data plane VCN 1218 (e.g. the data plane1018 of FIG. 10 ) via an LPG 1210 contained in the data plane VCN 1218.The control plane VCN 1216 and the data plane VCN 1218 can be containedin a service tenancy 1219 (e.g. the service tenancy 1019 of FIG. 10 ).

The control plane VCN 1216 can include a control plane DMZ tier 1220(e.g. the control plane DMZ tier 1020 of FIG. 10 ) that can include loadbalancer (LB) subnet(s) 1222 (e.g. LB subnet(s) 1022 of FIG. 10 ), acontrol plane app tier 1224 (e.g. the control plane app tier 1024 ofFIG. 10 ) that can include app subnet(s) 1226 (e.g. similar to appsubnet(s) 1026 of FIG. 10 ), a control plane data tier 1228 (e.g. thecontrol plane data tier 1028 of FIG. 10 ) that can include DB subnet(s)1230. The LB subnet(s) 1222 contained in the control plane DMZ tier 1220can be communicatively coupled to the app subnet(s) 1226 contained inthe control plane app tier 1224 and to an Internet gateway 1234 (e.g.the Internet gateway 1034 of FIG. 10 ) that can be contained in thecontrol plane VCN 1216, and the app subnet(s) 1226 can becommunicatively coupled to the DB subnet(s) 1230 contained in thecontrol plane data tier 1228 and to a service gateway 1236 (e.g. theservice gateway of FIG. 10 ) and a network address translation (NAT)gateway 1238 (e.g. the NAT gateway 1038 of FIG. 10 ). The control planeVCN 1216 can include the service gateway 1236 and the NAT gateway 1238.

The data plane VCN 1218 can include a data plane app tier 1246 (e.g. thedata plane app tier 1046 of FIG. 10 ), a data plane DMZ tier 1248 (e.g.the data plane DMZ tier 1048 of FIG. 10 ), and a data plane data tier1250 (e.g. the data plane data tier 1050 of FIG. 10 ). The data planeDMZ tier 1248 can include LB subnet(s) 1222 that can be communicativelycoupled to trusted app subnet(s) 1260 and untrusted app subnet(s) 1262of the data plane app tier 1246 and the Internet gateway 1234 containedin the data plane VCN 1218. The trusted app subnet(s) 1260 can becommunicatively coupled to the service gateway 1236 contained in thedata plane VCN 1218, the NAT gateway 1238 contained in the data planeVCN 1218, and DB subnet(s) 1230 contained in the data plane data tier1250. The untrusted app subnet(s) 1262 can be communicatively coupled tothe service gateway 1236 contained in the data plane VCN 1218 and DBsubnet(s) 1230 contained in the data plane data tier 1250. The dataplane data tier 1250 can include DB subnet(s) 1230 that can becommunicatively coupled to the service gateway 1236 contained in thedata plane VCN 1218.

The untrusted app subnet(s) 1262 can include one or more primary VNICs1264(1)-(N) that can be communicatively coupled to tenant virtualmachines (VMs) 1266(1)-(N). Each tenant VM 1266(1)-(N) can becommunicatively coupled to a respective app subnet 1267(1)-(N) that canbe contained in respective container egress VCNs 1268(1)-(N) that can becontained in respective customer tenancies 1270(1)-(N). Respectivesecondary VNICs 1272(1)-(N) can facilitate communication between theuntrusted app subnet(s) 1262 contained in the data plane VCN 1218 andthe app subnet contained in the container egress VCNs 1268(1)-(N). Eachcontainer egress VCNs 1268(1)-(N) can include a NAT gateway 1238 thatcan be communicatively coupled to public Internet 1254 (e.g. publicInternet 1054 of FIG. 10 ).

The Internet gateway 1234 contained in the control plane VCN 1216 andcontained in the data plane VCN 1218 can be communicatively coupled to ametadata management service 1252 (e.g. the metadata management system1052 of FIG. 10 ) that can be communicatively coupled to public Internet1254. Public Internet 1254 can be communicatively coupled to the NATgateway 1238 contained in the control plane VCN 1216 and contained inthe data plane VCN 1218. The service gateway 1236 contained in thecontrol plane VCN 1216 and contained in the data plane VCN 1218 can becommunicatively couple to cloud services 1256.

In some embodiments, the data plane VCN 1218 can be integrated withcustomer tenancies 1270. This integration can be useful or desirable forcustomers of the IaaS provider in some cases such as a case that maydesire support when executing code. The customer may provide code to runthat may be destructive, may communicate with other customer resources,or may otherwise cause undesirable effects. In response to this, theIaaS provider may determine whether to run code given to the IaaSprovider by the customer.

In some examples, the customer of the IaaS provider may grant temporarynetwork access to the IaaS provider and request a function to beattached to the data plane tier app 1246. Code to run the function maybe executed in the VMs 1266(1)-(N), and the code may not be configuredto run anywhere else on the data plane VCN 1218. Each VM 1266(1)-(N) maybe connected to one customer tenancy 1270. Respective containers1271(1)-(N) contained in the VMs 1266(1)-(N) may be configured to runthe code. In this case, there can be a dual isolation (e.g., thecontainers 1271(1)-(N) running code, where the containers 1271(1)-(N)may be contained in at least the VM 1266(1)-(N) that are contained inthe untrusted app subnet(s) 1262), which may help prevent incorrect orotherwise undesirable code from damaging the network of the IaaSprovider or from damaging a network of a different customer. Thecontainers 1271(1)-(N) may be communicatively coupled to the customertenancy 1270 and may be configured to transmit or receive data from thecustomer tenancy 1270. The containers 1271(1)-(N) may not be configuredto transmit or receive data from any other entity in the data plane VCN1218. Upon completion of running the code, the IaaS provider may kill orotherwise dispose of the containers 1271(1)-(N).

In some embodiments, the trusted app subnet(s) 1260 may run code thatmay be owned or operated by the IaaS provider. In this embodiment, thetrusted app subnet(s) 1260 may be communicatively coupled to the DBsubnet(s) 1230 and be configured to execute CRUD operations in the DBsubnet(s) 1230. The untrusted app subnet(s) 1262 may be communicativelycoupled to the DB subnet(s) 1230, but in this embodiment, the untrustedapp subnet(s) may be configured to execute read operations in the DBsubnet(s) 1230. The containers 1271(1)-(N) that can be contained in theVM 1266(1)-(N) of each customer and that may run code from the customermay not be communicatively coupled with the DB subnet(s) 1230.

In other embodiments, the control plane VCN 1216 and the data plane VCN1218 may not be directly communicatively coupled. In this embodiment,there may be no direct communication between the control plane VCN 1216and the data plane VCN 1218. However, communication can occur indirectlythrough at least one method. An LPG 1210 may be established by the IaaSprovider that can facilitate communication between the control plane VCN1216 and the data plane VCN 1218. In another example, the control planeVCN 1216 or the data plane VCN 1218 can make a call to cloud services1256 via the service gateway 1236. For example, a call to cloud services1256 from the control plane VCN 1216 can include a request for a servicethat can communicate with the data plane VCN 1218.

FIG. 13 is a block diagram 1300 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1302 (e.g. service operators 1002 of FIG. 10 ) can becommunicatively coupled to a secure host tenancy 1304 (e.g. the securehost tenancy 1004 of FIG. 10 ) that can include a virtual cloud network(VCN) 1306 (e.g. the VCN 1006 of FIG. 10 ) and a secure host subnet 1308(e.g. the secure host subnet 1008 of FIG. 10 ). The VCN 1306 can includean LPG 1310 (e.g. the LPG 1010 of FIG. 10 ) that can be communicativelycoupled to an SSH VCN 1312 (e.g. the SSH VCN 1012 of FIG. 10 ) via anLPG 1310 contained in the SSH VCN 1312. The SSH VCN 1312 can include anSSH subnet 1314 (e.g. the SSH subnet 1014 of FIG. 10 ), and the SSH VCN1312 can be communicatively coupled to a control plane VCN 1316 (e.g.the control plane VCN 1016 of FIG. 10 ) via an LPG 1310 contained in thecontrol plane VCN 1316 and to a data plane VCN 1318 (e.g. the data plane1018 of FIG. 10 ) via an LPG 1310 contained in the data plane VCN 1318.The control plane VCN 1316 and the data plane VCN 1318 can be containedin a service tenancy 1319 (e.g. the service tenancy 1019 of FIG. 10 ).

The control plane VCN 1316 can include a control plane DMZ tier 1320(e.g. the control plane DMZ tier 1020 of FIG. 10 ) that can include LBsubnet(s) 1322 (e.g. LB subnet(s) 1022 of FIG. 10 ), a control plane apptier 1324 (e.g. the control plane app tier 1024 of FIG. 10 ) that caninclude app subnet(s) 1326 (e.g. app subnet(s) 1026 of FIG. 10 ), acontrol plane data tier 1328 (e.g. the control plane data tier 1028 ofFIG. 10 ) that can include DB subnet(s) 1330 (e.g. DB subnet(s) 1230 ofFIG. 12 ). The LB subnet(s) 1322 contained in the control plane DMZ tier1320 can be communicatively coupled to the app subnet(s) 1326 containedin the control plane app tier 1324 and to an Internet gateway 1334 (e.g.the Internet gateway 1034 of FIG. 10 ) that can be contained in thecontrol plane VCN 1316, and the app subnet(s) 1326 can becommunicatively coupled to the DB subnet(s) 1330 contained in thecontrol plane data tier 1328 and to a service gateway 1336 (e.g. theservice gateway of FIG. 10 ) and a network address translation (NAT)gateway 1338 (e.g. the NAT gateway 1038 of FIG. 10 ). The control planeVCN 1316 can include the service gateway 1336 and the NAT gateway 1338.

The data plane VCN 1318 can include a data plane app tier 1346 (e.g. thedata plane app tier 1046 of FIG. 10 ), a data plane DMZ tier 1348 (e.g.the data plane DMZ tier 1048 of FIG. 10 ), and a data plane data tier1350 (e.g. the data plane data tier 1050 of FIG. 10 ). The data planeDMZ tier 1348 can include LB subnet(s) 1322 that can be communicativelycoupled to trusted app subnet(s) 1360 (e.g. trusted app subnet(s) 1260of FIG. 12 ) and untrusted app subnet(s) 1362 (e.g. untrusted appsubnet(s) 1262 of FIG. 12 ) of the data plane app tier 1346 and theInternet gateway 1334 contained in the data plane VCN 1318. The trustedapp subnet(s) 1360 can be communicatively coupled to the service gateway1336 contained in the data plane VCN 1318, the NAT gateway 1338contained in the data plane VCN 1318, and DB subnet(s) 1330 contained inthe data plane data tier 1350. The untrusted app subnet(s) 1362 can becommunicatively coupled to the service gateway 1336 contained in thedata plane VCN 1318 and DB subnet(s) 1330 contained in the data planedata tier 1350. The data plane data tier 1350 can include DB subnet(s)1330 that can be communicatively coupled to the service gateway 1336contained in the data plane VCN 1318.

The untrusted app subnet(s) 1362 can include primary VNICs 1364(1)-(N)that can be communicatively coupled to tenant virtual machines (VMs)1366(1)-(N) residing within the untrusted app subnet(s) 1362. Eachtenant VM 1366(1)-(N) can run code in a respective container1367(1)-(N), and be communicatively coupled to an app subnet 1326 thatcan be contained in a data plane app tier 1346 that can be contained ina container egress VCN 1368. Respective secondary VNICs 1372(1)-(N) canfacilitate communication between the untrusted app subnet(s) 1362contained in the data plane VCN 1318 and the app subnet contained in thecontainer egress VCN 1368. The container egress VCN can include a NATgateway 1338 that can be communicatively coupled to public Internet 1354(e.g. public Internet 1054 of FIG. 10 ).

The Internet gateway 1334 contained in the control plane VCN 1316 andcontained in the data plane VCN 1318 can be communicatively coupled to ametadata management service 1352 (e.g. the metadata management system1052 of FIG. 10 ) that can be communicatively coupled to public Internet1354. Public Internet 1354 can be communicatively coupled to the NATgateway 1338 contained in the control plane VCN 1316 and contained inthe data plane VCN 1318. The service gateway 1336 contained in thecontrol plane VCN 1316 and contained in the data plane VCN 1318 can becommunicatively couple to cloud services 1356.

In some examples, the pattern illustrated by the architecture of blockdiagram 1300 of FIG. 13 may be considered an exception to the patternillustrated by the architecture of block diagram 1200 of FIG. 12 and maybe desirable for a customer of the IaaS provider if the IaaS providercannot directly communicate with the customer (e.g., a disconnectedregion). The respective containers 1367(1)-(N) that are contained in theVMs 1366(1)-(N) for each customer can be accessed in real-time by thecustomer. The containers 1367(1)-(N) may be configured to make calls torespective secondary VNICs 1372(1)-(N) contained in app subnet(s) 1326of the data plane app tier 1346 that can be contained in the containeregress VCN 1368. The secondary VNICs 1372(1)-(N) can transmit the callsto the NAT gateway 1338 that may transmit the calls to public Internet1354. In this example, the containers 1367(1)-(N) that can be accessedin real-time by the customer can be isolated from the control plane VCN1316 and can be isolated from other entities contained in the data planeVCN 1318. The containers 1367(1)-(N) may also be isolated from resourcesfrom other customers.

In other examples, the customer can use the containers 1367(1)-(N) tocall cloud services 1356. In this example, the customer may run code inthe containers 1367(1)-(N) that requests a service from cloud services1356. The containers 1367(1)-(N) can transmit this request to thesecondary VNICs 1372(1)-(N) that can transmit the request to the NATgateway that can transmit the request to public Internet 1354. PublicInternet 1354 can transmit the request to LB subnet(s) 1322 contained inthe control plane VCN 1316 via the Internet gateway 1334. In response todetermining the request is valid, the LB subnet(s) can transmit therequest to app subnet(s) 1326 that can transmit the request to cloudservices 1356 via the service gateway 1336.

It should be appreciated that IaaS architectures 1000, 1100, 1200, 1300depicted in the figures may have other components than those depicted.Further, the embodiments shown in the figures are only some examples ofa cloud infrastructure system that may incorporate an embodiment of thedisclosure. In some other embodiments, the IaaS systems may have more orfewer components than shown in the figures, may combine two or morecomponents, or may have a different configuration or arrangement ofcomponents.

In certain embodiments, the IaaS systems described herein may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such an IaaS system is the Oracle Cloud Infrastructure (OCI)provided by the present assignee.

FIG. 14 illustrates an example computer system 1400, in which variousembodiments of the present disclosure may be implemented. The system1400 may be used to implement any of the computer systems describedabove. As shown in the figure, computer system 1400 includes aprocessing unit 1404 that communicates with a number of peripheralsubsystems via a bus subsystem 1402. These peripheral subsystems mayinclude a processing acceleration unit 1406, an I/O subsystem 1408, astorage subsystem 1418 and a communications subsystem 1424. Storagesubsystem 1418 includes tangible computer-readable storage media 1422and a system memory 1410.

Bus subsystem 1402 provides a mechanism for letting the variouscomponents and subsystems of computer system 1400 communicate with eachother as intended. Although bus subsystem 1402 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 1402 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Forexample, such architectures may include an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 1404, which can be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 1400. One or more processorsmay be included in processing unit 1404. These processors may includesingle core or multicore processors. In certain embodiments, processingunit 1404 may be implemented as one or more independent processing units1432 and/or 1434 with single or multicore processors included in eachprocessing unit. In other embodiments, processing unit 1404 may also beimplemented as a quad-core processing unit formed by integrating twodual-core processors into a single chip.

In various embodiments, processing unit 1404 can execute a variety ofprograms in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processor(s)1404 and/or in storage subsystem 1418. Through suitable programming,processor(s) 1404 can provide various functionalities described above.Computer system 1400 may additionally include a processing accelerationunit 1406, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

I/O subsystem 1408 may include user interface input devices and userinterface output devices. User interface input devices may include akeyboard, pointing devices such as a mouse or trackball, a touchpad ortouch screen incorporated into a display, a scroll wheel, a click wheel,a dial, a button, a switch, a keypad, audio input devices with voicecommand recognition systems, microphones, and other types of inputdevices. User interface input devices may include, for example, motionsensing and/or gesture recognition devices such as the Microsoft Kinect®motion sensor that enables users to control and interact with an inputdevice, such as the Microsoft Xbox® 360 game controller, through anatural user interface using gestures and spoken commands. Userinterface input devices may also include eye gesture recognition devicessuch as the Google Glass® blink detector that detects eye activity(e.g., ‘blinking’ while taking pictures and/or making a menu selection)from users and transforms the eye gestures as input into an input device(e.g., Google Glass®). Additionally, user interface input devices mayinclude voice recognition sensing devices that enable users to interactwith voice recognition systems (e.g., Siri® navigator), through voicecommands.

User interface input devices may also include, without limitation, threedimensional (3D) mice, joysticks or pointing sticks, gamepads andgraphic tablets, and audio/visual devices such as speakers, digitalcameras, digital camcorders, portable media players, webcams, imagescanners, fingerprint scanners, barcode reader 3D scanners, 3D printers,laser rangefinders, and eye gaze tracking devices. Additionally, userinterface input devices may include, for example, medical imaging inputdevices such as computed tomography, magnetic resonance imaging,position emission tomography, medical ultrasonography devices. Userinterface input devices may also include, for example, audio inputdevices such as MIDI keyboards, digital musical instruments and thelike.

User interface output devices may include a display subsystem, indicatorlights, or non-visual displays such as audio output devices, etc. Thedisplay subsystem may be a cathode ray tube (CRT), a flat-panel device,such as that using a liquid crystal display (LCD) or plasma display, aprojection device, a touch screen, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system1400 to a user or other computer. For example, user interface outputdevices may include, without limitation, a variety of display devicesthat visually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Computer system 1400 may comprise a storage subsystem 1418 thatcomprises software elements, shown as being currently located within asystem memory 1410. System memory 1410 may store program instructionsthat are loadable and executable on processing unit 1404, as well asdata generated during the execution of these programs.

Depending on the configuration and type of computer system 1400, systemmemory 1410 may be volatile (such as random access memory (RAM)) and/ornon-volatile (such as read-only memory (ROM), flash memory, etc.) TheRAM typically contains data and/or program modules that are immediatelyaccessible to and/or presently being operated and executed by processingunit 1404. In some implementations, system memory 1410 may includemultiple different types of memory, such as static random access memory(SRAM) or dynamic random access memory (DRAM). In some implementations,a basic input/output system (BIOS), containing the basic routines thathelp to transfer information between elements within computer system1400, such as during start-up, may typically be stored in the ROM. Byway of example, and not limitation, system memory 1410 also illustratesapplication programs 1412, which may include client applications, Webbrowsers, mid-tier applications, relational database management systems(RDBMS), etc., program data 1414, and an operating system 1416. By wayof example, operating system 1416 may include various versions ofMicrosoft Windows®, Apple Macintosh®, and/or Linux operating systems, avariety of commercially-available UNIX® or UNIX-like operating systems(including without limitation the variety of GNU/Linux operatingsystems, the Google Chrome® OS, and the like) and/or mobile operatingsystems such as iOS, Windows® Phone, Android® OS, BlackBerry® 14 OS, andPalm® OS operating systems.

Storage subsystem 1418 may also provide a tangible computer-readablestorage medium for storing the basic programming and data constructsthat provide the functionality of some embodiments. Software (programs,code modules, instructions) that when executed by a processor providethe functionality described above may be stored in storage subsystem1418. These software modules or instructions may be executed byprocessing unit 1404. Storage subsystem 1418 may also provide arepository for storing data used in accordance with the presentdisclosure.

Storage subsystem 1400 may also include a computer-readable storagemedia reader 1420 that can further be connected to computer-readablestorage media 1422. Together and, optionally, in combination with systemmemory 1410, computer-readable storage media 1422 may comprehensivelyrepresent remote, local, fixed, and/or removable storage devices plusstorage media for temporarily and/or more permanently containing,storing, transmitting, and retrieving computer-readable information.

Computer-readable storage media 1422 containing code, or portions ofcode, can also include any appropriate media known or used in the art,including storage media and communication media, such as but not limitedto, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This can include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This can also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium which can be used to transmit thedesired information and which can be accessed by computing system 1400.

By way of example, computer-readable storage media 1422 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 1422 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 1422 may also include,solid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 1400.

Communications subsystem 1424 provides an interface to other computersystems and networks. Communications subsystem 1424 serves as aninterface for receiving data from and transmitting data to other systemsfrom computer system 1400. For example, communications subsystem 1424may enable computer system 1400 to connect to one or more devices viathe Internet. In some embodiments communications subsystem 1424 caninclude radio frequency (RF) transceiver components for accessingwireless voice and/or data networks (e.g., using cellular telephonetechnology, advanced data network technology, such as 3G, 4G or EDGE(enhanced data rates for global evolution), WiFi (IEEE 802.11 familystandards, or other mobile communication technologies, or anycombination thereof), global positioning system (GPS) receivercomponents, and/or other components. In some embodiments communicationssubsystem 1424 can provide wired network connectivity (e.g., Ethernet)in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 1424 may also receiveinput communication in the form of structured and/or unstructured datafeeds 1426, event streams 1428, event updates 1430, and the like onbehalf of one or more users who may use computer system 1400.

By way of example, communications subsystem 1424 may be configured toreceive data feeds 1426 in real-time from users of social networksand/or other communication services such as Twitter® feeds, Facebook®updates, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources.

Additionally, communications subsystem 1424 may also be configured toreceive data in the form of continuous data streams, which may includeevent streams 1428 of real-time events and/or event updates 1430, thatmay be continuous or unbounded in nature with no explicit end. Examplesof applications that generate continuous data may include, for example,sensor data applications, financial tickers, network performancemeasuring tools (e.g. network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like.

Communications subsystem 1424 may also be configured to output thestructured and/or unstructured data feeds 1426, event streams 1428,event updates 1430, and the like to one or more databases that may be incommunication with one or more streaming data source computers coupledto computer system 1400.

Computer system 1400 can be one of various types, including a handheldportable device (e.g., an iPhone® cellular phone, an iPad® computingtablet, a PDA), a wearable device (e.g., a Google Glass® head mounteddisplay), a PC, a workstation, a mainframe, a kiosk, a server rack, orany other data processing system.

Due to the ever-changing nature of computers and networks, thedescription of computer system 1400 depicted in the figure is intendedonly as a specific example. Many other configurations having more orfewer components than the system depicted in the figure are possible.For example, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software (includingapplets), or a combination. Further, connection to other computingdevices, such as network input/output devices, may be employed. Based onthe disclosure and teachings provided herein, a person of ordinary skillin the art will appreciate other ways and/or methods to implement thevarious embodiments.

The term cloud service is generally used to refer to a service that ismade available by a cloud services provider (CSP) to users or customerson demand (e.g., via a subscription model) using systems andinfrastructure (cloud infrastructure) provided by the CSP. Typically,the servers and systems that make up the CSP's infrastructure areseparate from the customer's own on-premise servers and systems.Customers can thus avail themselves of cloud services provided by theCSP without having to purchase separate hardware and software resourcesfor the services. Cloud services are designed to provide a subscribingcustomer easy, scalable access to applications and computing resourceswithout the customer having to invest in procuring the infrastructurethat is used for providing the services.

There are several cloud service providers that offer various types ofcloud services. There are various different types or models of cloudservices including Software-as-a-Service (SaaS), Platform-as-a-Service(PaaS), Infrastructure-as-a-Service (IaaS), and others.

A customer can subscribe to one or more cloud services provided by aCSP. The customer can be any entity such as an individual, anorganization, an enterprise, and the like. When a customer subscribes toor registers for a service provided by a CSP, a tenancy or an account iscreated for that customer. The customer can then, via this account,access the subscribed-to one or more cloud resources associated with theaccount.

As noted above, infrastructure as a service (IaaS) is one particulartype of cloud computing service. In an IaaS model, the CSP providesinfrastructure (referred to as cloud services provider infrastructure orCSPI) that can be used by customers to build their own customizablenetworks and deploy customer resources. The customer's resources andnetworks are thus hosted in a distributed environment by infrastructureprovided by a CSP. This is different from traditional computing, wherethe customer's resources and networks are hosted by infrastructureprovided by the customer.

The CSPI may comprise interconnected high-performance compute resourcesincluding various host machines, memory resources, and network resourcesthat form a physical network, which is also referred to as a substratenetwork or an underlay network. The resources in CSPI may be spreadacross one or more data centers that may be geographically spread acrossone or more geographical regions. Virtualization software may beexecuted by these physical resources to provide a virtualizeddistributed environment. The virtualization creates an overlay network(also known as a software-based network, a software-defined network, ora virtual network) over the physical network. The CSPI physical networkprovides the underlying basis for creating one or more overlay orvirtual networks on top of the physical network. The virtual or overlaynetworks can include one or more virtual cloud networks (VCNs). Thevirtual networks are implemented using software virtualizationtechnologies (e.g., hypervisors, functions performed by networkvirtualization devices (NVDs) (e.g., smartNICs), top-of-rack (TOR)switches, smart TORs that implement one or more functions performed byan NVD, and other mechanisms) to create layers of network abstractionthat can be run on top of the physical network. Virtual networks cantake on many forms, including peer-to-peer networks, IP networks, andothers. Virtual networks are typically either Layer-3 IP networks orLayer-2 VLANs. This method of virtual or overlay networking is oftenreferred to as virtual or overlay Layer-3 networking. Examples ofprotocols developed for virtual networks include IP-in-IP (or GenericRouting Encapsulation (GRE)), Virtual Extensible LAN (VXLAN—IETF RFC7348), Virtual Private Networks (VPNs) (e.g., MPLS Layer-3 VirtualPrivate Networks (RFC 4364)), VMware's NSX, GENEVE (Generic NetworkVirtualization Encapsulation), and others.

For IaaS, the infrastructure (CSPI) provided by a CSP can be configuredto provide virtualized computing resources over a public network (e.g.,the Internet). In an IaaS model, a cloud computing services provider canhost the infrastructure components (e.g., servers, storage devices,network nodes (e.g., hardware), deployment software, platformvirtualization (e.g., a hypervisor layer), or the like). In some cases,an IaaS provider may also supply a variety of services to accompanythose infrastructure components (e.g., billing, monitoring, logging,security, load balancing and clustering, etc.). Thus, as these servicesmay be policy-driven, IaaS users may be able to implement policies todrive load balancing to maintain application availability andperformance. CSPI provides infrastructure and a set of complementarycloud services that enable customers to build and run a wide range ofapplications and services in a highly available hosted distributedenvironment. CSPI offers high-performance compute resources andcapabilities and storage capacity in a flexible virtual network that issecurely accessible from various networked locations such as from acustomer's on-premises network. When a customer subscribes to orregisters for an IaaS service provided by a CSP, the tenancy created forthat customer is a secure and isolated partition within the CSPI wherethe customer can create, organize, and administer their cloud resources.

Customers can build their own virtual networks using compute, memory,and networking resources provided by CSPI. One or more customerresources or workloads, such as compute instances, can be deployed onthese virtual networks. For example, a customer can use resourcesprovided by CSPI to build one or multiple customizable and privatevirtual network(s) referred to as virtual cloud networks (VCNs). Acustomer can deploy one or more customer resources, such as computeinstances, on a customer VCN. Compute instances can take the form ofvirtual machines, bare metal instances, and the like. The CSPI thusprovides infrastructure and a set of complementary cloud services thatenable customers to build and run a wide range of applications andservices in a highly available virtual hosted environment. The customerdoes not manage or control the underlying physical resources provided byCSPI but has control over operating systems, storage, and deployedapplications; and possibly limited control of select networkingcomponents (e.g., firewalls).

The CSP may provide a console that enables customers and networkadministrators to configure, access, and manage resources deployed inthe cloud using CSPI resources. In certain embodiments, the consoleprovides a web-based user interface that can be used to access andmanage CSPI. In some implementations, the console is a web-basedapplication provided by the CSP.

CSPI may support single-tenancy or multi-tenancy architectures. In asingle tenancy architecture, a software (e.g., an application, adatabase) or a hardware component (e.g., a host machine or a server)serves a single customer or tenant. In a multi-tenancy architecture, asoftware or a hardware component serves multiple customers or tenants.Thus, in a multi-tenancy architecture, CSPI resources are shared betweenmultiple customers or tenants. In a multi-tenancy situation, precautionsare taken and safeguards put in place within CSPI to ensure that eachtenant's data is isolated and remains invisible to other tenants.

In a physical network, a network endpoint (“endpoint”) refers to acomputing device or system that is connected to a physical network andcommunicates back and forth with the network to which it is connected. Anetwork endpoint in the physical network may be connected to a LocalArea Network (LAN), a Wide Area Network (WAN), or other type of physicalnetwork. Examples of traditional endpoints in a physical network includemodems, hubs, bridges, switches, routers, and other networking devices,physical computers (or host machines), and the like. Each physicaldevice in the physical network has a fixed network address that can beused to communicate with the device. This fixed network address can be aLayer-2 address (e.g., a MAC address), a fixed Layer-3 address (e.g., anIP address), and the like. In a virtualized environment or in a virtualnetwork, the endpoints can include various virtual endpoints such asvirtual machines that are hosted by components of the physical network(e.g., hosted by physical host machines). These endpoints in the virtualnetwork are addressed by overlay addresses such as overlay Layer-2addresses (e.g., overlay MAC addresses) and overlay Layer-3 addresses(e.g., overlay IP addresses). Network overlays enable flexibility byallowing network managers to move around the overlay addressesassociated with network endpoints using software management (e.g., viasoftware implementing a control plane for the virtual network).Accordingly, unlike in a physical network, in a virtual network, anoverlay address (e.g., an overlay IP address) can be moved from oneendpoint to another using network management software. Since the virtualnetwork is built on top of a physical network, communications betweencomponents in the virtual network involves both the virtual network andthe underlying physical network. In order to facilitate suchcommunications, the components of CSPI are configured to learn and storemappings that map overlay addresses in the virtual network to actualphysical addresses in the substrate network, and vice versa. Thesemappings are then used to facilitate the communications. Customertraffic is encapsulated to facilitate routing in the virtual network.

Accordingly, physical addresses (e.g., physical IP addresses) areassociated with components in physical networks and overlay addresses(e.g., overlay IP addresses) are associated with entities in virtualnetworks. Both the physical IP addresses and overlay IP addresses aretypes of real IP addresses. These are separate from virtual IPaddresses, where a virtual IP address maps to multiple real IPaddresses. A virtual IP address provides a 1-to-many mapping between thevirtual IP address and multiple real IP addresses.

The cloud infrastructure or CSPI is physically hosted in one or moredata centers in one or more regions around the world. The CSPI mayinclude components in the physical or substrate network and virtualizedcomponents (e.g., virtual networks, compute instances, virtual machines,etc.) that are in an virtual network built on top of the physicalnetwork components. In certain embodiments, the CSPI is organized andhosted in realms, regions and availability domains. A region istypically a localized geographic area that contains one or more datacenters. Regions are generally independent of each other and can beseparated by vast distances, for example, across countries or evencontinents. For example, a first region may be in Australia, another onein Japan, yet another one in India, and the like. CSPI resources aredivided among regions such that each region has its own independentsubset of CSPI resources. Each region may provide a set of coreinfrastructure services and resources, such as, compute resources (e.g.,bare metal servers, virtual machine, containers and relatedinfrastructure, etc.); storage resources (e.g., block volume storage,file storage, object storage, archive storage); networking resources(e.g., virtual cloud networks (VCNs), load balancing resources,connections to on-premise networks), database resources; edge networkingresources (e.g., DNS); and access management and monitoring resources,and others. Each region generally has multiple paths connecting it toother regions in the realm.

Generally, an application is deployed in a region (i.e., deployed oninfrastructure associated with that region) where it is most heavilyused, because using nearby resources is faster than using distantresources. Applications can also be deployed in different regions forvarious reasons, such as redundancy to mitigate the risk of region-wideevents such as large weather systems or earthquakes, to meet varyingrequirements for legal jurisdictions, tax domains, and other business orsocial criteria, and the like.

The data centers within a region can be further organized and subdividedinto availability domains (ADs). An availability domain may correspondto one or more data centers located within a region. A region can becomposed of one or more availability domains. In such a distributedenvironment, CSPI resources are either region-specific, such as avirtual cloud network (VCN), or availability domain-specific, such as acompute instance.

ADs within a region are isolated from each other, fault tolerant, andare configured such that they are very unlikely to fail simultaneously.This is achieved by the ADs not sharing critical infrastructureresources such as networking, physical cables, cable paths, cable entrypoints, etc., such that a failure at one AD within a region is unlikelyto impact the availability of the other ADs within the same region. TheADs within the same region may be connected to each other by a lowlatency, high bandwidth network, which makes it possible to providehigh-availability connectivity to other networks (e.g., the Internet,customers' on-premise networks, etc.) and to build replicated systems inmultiple ADs for both high-availability and disaster recovery. Cloudservices use multiple ADs to ensure high availability and to protectagainst resource failure. As the infrastructure provided by the IaaSprovider grows, more regions and ADs may be added with additionalcapacity. Traffic between availability domains is usually encrypted.

In certain embodiments, regions are grouped into realms. A realm is alogical collection of regions. Realms are isolated from each other anddo not share any data. Regions in the same realm may communicate witheach other, but regions in different realms cannot. A customer's tenancyor account with the CSP exists in a single realm and can be spreadacross one or more regions that belong to that realm. Typically, when acustomer subscribes to an IaaS service, a tenancy or account is createdfor that customer in the customer-specified region (referred to as the“home” region) within a realm. A customer can extend the customer'stenancy across one or more other regions within the realm. A customercannot access regions that are not in the realm where the customer'stenancy exists.

An IaaS provider can provide multiple realms, each realm catered to aparticular set of customers or users. For example, a commercial realmmay be provided for commercial customers. As another example, a realmmay be provided for a specific country for customers within thatcountry. As yet another example, a government realm may be provided fora government, and the like. For example, the government realm may becatered for a specific government and may have a heightened level ofsecurity than a commercial realm. For example, Oracle CloudInfrastructure (OCI) currently offers a realm for commercial regions andtwo realms (e.g., FedRAMP authorized and IL5 authorized) for governmentcloud regions.

In certain embodiments, an AD can be subdivided into one or more faultdomains. A fault domain is a grouping of infrastructure resources withinan AD to provide anti-affinity. Fault domains allow for the distributionof compute instances such that the instances are not on the samephysical hardware within a single AD. This is known as anti-affinity. Afault domain refers to a set of hardware components (computers,switches, and more) that share a single point of failure. A compute poolis logically divided up into fault domains. Due to this, a hardwarefailure or compute hardware maintenance event that affects one faultdomain does not affect instances in other fault domains. Depending onthe embodiment, the number of fault domains for each AD may vary. Forinstance, in certain embodiments each AD contains three fault domains. Afault domain acts as a logical data center within an AD.

When a customer subscribes to an IaaS service, resources from CSPI areprovisioned for the customer and associated with the customer's tenancy.The customer can use these provisioned resources to build privatenetworks and deploy resources on these networks. The customer networksthat are hosted in the cloud by the CSPI are referred to as virtualcloud networks (VCNs). A customer can set up one or more virtual cloudnetworks (VCNs) using CSPI resources allocated for the customer. A VCNis a virtual or software defined private network. The customer resourcesthat are deployed in the customer's VCN can include compute instances(e.g., virtual machines, bare-metal instances) and other resources.These compute instances may represent various customer workloads such asapplications, load balancers, databases, and the like. A computeinstance deployed on a VCN can communicate with public accessibleendpoints (“public endpoints”) over a public network such as theInternet, with other instances in the same VCN or other VCNs (e.g., thecustomer's other VCNs, or VCNs not belonging to the customer), with thecustomer's on-premise data centers or networks, and with serviceendpoints, and other types of endpoints.

The CSP may provide various services using the CSPI. In some instances,customers of CSPI may themselves act like service providers and provideservices using CSPI resources. A service provider may expose a serviceendpoint, which is characterized by identification information (e.g., anIP Address, a DNS name and port). A customer's resource (e.g., a computeinstance) can consume a particular service by accessing a serviceendpoint exposed by the service for that particular service. Theseservice endpoints are generally endpoints that are publicly accessibleby users using public IP addresses associated with the endpoints via apublic communication network such as the Internet. Network endpointsthat are publicly accessible are also sometimes referred to as publicendpoints.

In certain embodiments, a service provider may expose a service via anendpoint (sometimes referred to as a service endpoint) for the service.Customers of the service can then use this service endpoint to accessthe service. In certain implementations, a service endpoint provided fora service can be accessed by multiple customers that intend to consumethat service. In other implementations, a dedicated service endpoint maybe provided for a customer such that only that customer can access theservice using that dedicated service endpoint.

In certain embodiments, when a VCN is created, it is associated with aprivate overlay Classless Inter-Domain Routing (CIDR) address space,which is a range of private overlay IP addresses that are assigned tothe VCN (e.g., 10.0/16). A VCN includes associated subnets, routetables, and gateways. A VCN resides within a single region but can spanone or more or all of the region's availability domains. A gateway is avirtual interface that is configured for a VCN and enables communicationof traffic to and from the VCN to one or more endpoints outside the VCN.One or more different types of gateways may be configured for a VCN toenable communication to and from different types of endpoints.

A VCN can be subdivided into one or more sub-networks such as one ormore subnets. A subnet is thus a unit of configuration or a subdivisionthat can be created within a VCN. A VCN can have one or multiplesubnets. Each subnet within a VCN is associated with a contiguous rangeof overlay IP addresses (e.g., 10.0.0.0/24 and 10.0.1.0/24) that do notoverlap with other subnets in that VCN and which represent an addressspace subset within the address space of the VCN.

Each compute instance is associated with a virtual network interfacecard (VNIC), that enables the compute instance to participate in asubnet of a VCN. A VNIC is a logical representation of physical NetworkInterface Card (NIC). In general. a VNIC is an interface between anentity (e.g., a compute instance, a service) and a virtual network. AVNIC exists in a subnet, has one or more associated IP addresses, andassociated security rules or policies. A VNIC is equivalent to a Layer-2port on a switch. A VNIC is attached to a compute instance and to asubnet within a VCN. A VNIC associated with a compute instance enablesthe compute instance to be a part of a subnet of a VCN and enables thecompute instance to communicate (e.g., send and receive packets) withendpoints that are on the same subnet as the compute instance, withendpoints in different subnets in the VCN, or with endpoints outside theVCN. The VNIC associated with a compute instance thus determines how thecompute instance connects with endpoints inside and outside the VCN. AVNIC for a compute instance is created and associated with that computeinstance when the compute instance is created and added to a subnetwithin a VCN. For a subnet comprising a set of compute instances, thesubnet contains the VNICs corresponding to the set of compute instances,each VNIC attached to a compute instance within the set of computerinstances.

Each compute instance is assigned a private overlay IP address via theVNIC associated with the compute instance. This private overlay IPaddress is assigned to the VNIC that is associated with the computeinstance when the compute instance is created and used for routingtraffic to and from the compute instance. All VNICs in a given subnetuse the same route table, security lists, and DHCP options. As describedabove, each subnet within a VCN is associated with a contiguous range ofoverlay IP addresses (e.g., 10.0.0.0/24 and 10.0.1.0/24) that do notoverlap with other subnets in that VCN and which represent an addressspace subset within the address space of the VCN. For a VNIC on aparticular subnet of a VCN, the private overlay IP address that isassigned to the VNIC is an address from the contiguous range of overlayIP addresses allocated for the subnet.

In certain embodiments, a compute instance may optionally be assignedadditional overlay IP addresses in addition to the private overlay IPaddress, such as, for example, one or more public IP addresses if in apublic subnet. These multiple addresses are assigned either on the sameVNIC or over multiple VNICs that are associated with the computeinstance. Each instance however has a primary VNIC that is createdduring instance launch and is associated with the overlay private IPaddress assigned to the instance—this primary VNIC cannot be removed.Additional VNICs, referred to as secondary VNICs, can be added to anexisting instance in the same availability domain as the primary VNIC.All the VNICs are in the same availability domain as the instance. Asecondary VNIC can be in a subnet in the same VCN as the primary VNIC,or in a different subnet that is either in the same VCN or a differentone.

A compute instance may optionally be assigned a public IP address if itis in a public subnet. A subnet can be designated as either a publicsubnet or a private subnet at the time the subnet is created. A privatesubnet means that the resources (e.g., compute instances) and associatedVNICs in the subnet cannot have public overlay IP addresses. A publicsubnet means that the resources and associated VNICs in the subnet canhave public IP addresses. A customer can designate a subnet to existeither in a single availability domain or across multiple availabilitydomains in a region or realm.

As described above, a VCN may be subdivided into one or more subnets. Incertain embodiments, a Virtual Router (VR) configured for the VCN(referred to as the VCN VR or just VR) enables communications betweenthe subnets of the VCN. For a subnet within a VCN, the VR represents alogical gateway for that subnet that enables the subnet (i.e., thecompute instances on that subnet) to communicate with endpoints on othersubnets within the VCN, and with other endpoints outside the VCN. TheVCN VR is a logical entity that is configured to route traffic betweenVNICs in the VCN and virtual gateways (“gateways”) associated with theVCN. Gateways are further described below with respect to FIG. 1 . A VCNVR is a Layer-3/IP Layer concept. In one embodiment, there is one VCN VRfor a VCN where the VCN VR has potentially an unlimited number of portsaddressed by IP addresses, with one port for each subnet of the VCN. Inthis manner, the VCN VR has a different IP address for each subnet inthe VCN that the VCN VR is attached to. The VR is also connected to thevarious gateways configured for a VCN. In certain embodiments, aparticular overlay IP address from the overlay IP address range for asubnet is reserved for a port of the VCN VR for that subnet. Forexample, consider a VCN having two subnets with associated addressranges 10.0/16 and 10.1/16, respectively. For the first subnet withinthe VCN with address range 10.0/16, an address from this range isreserved for a port of the VCN VR for that subnet. In some instances,the first IP address from the range may be reserved for the VCN VR. Forexample, for the subnet with overlay IP address range 10.0/16, IPaddress 10.0.0.1 may be reserved for a port of the VCN VR for thatsubnet. For the second subnet within the same VCN with address range10.1/16, the VCN VR may have a port for that second subnet with IPaddress 10.1.0.1. The VCN VR has a different IP address for each of thesubnets in the VCN.

In some other embodiments, each subnet within a VCN may have its ownassociated VR that is addressable by the subnet using a reserved ordefault IP address associated with the VR. The reserved or default IPaddress may, for example, be the first IP address from the range of IPaddresses associated with that subnet. The VNICs in the subnet cancommunicate (e.g., send and receive packets) with the VR associated withthe subnet using this default or reserved IP address. In such anembodiment, the VR is the ingress/egress point for that subnet. The VRassociated with a subnet within the VCN can communicate with other VRsassociated with other subnets within the VCN. The VRs can alsocommunicate with gateways associated with the VCN. The VR function for asubnet is running on or executed by one or more NVDs executing VNICsfunctionality for VNICs in the subnet.

Route tables, security rules, and DHCP options may be configured for aVCN. Route tables are virtual route tables for the VCN and include rulesto route traffic from subnets within the VCN to destinations outside theVCN by way of gateways or specially configured instances. A VCN's routetables can be customized to control how packets are forwarded/routed toand from the VCN. DHCP options refers to configuration information thatis automatically provided to the instances when they boot up.

Security rules configured for a VCN represent overlay firewall rules forthe VCN. The security rules can include ingress and egress rules, andspecify the types of traffic (e.g., based upon protocol and port) thatis allowed in and out of the instances within the VCN. The customer canchoose whether a given rule is stateful or stateless. For instance, thecustomer can allow incoming SSH traffic from anywhere to a set ofinstances by setting up a stateful ingress rule with source CIDR0.0.0.0/0, and destination TCP port 22. Security rules can beimplemented using network security groups or security lists. A networksecurity group consists of a set of security rules that apply only tothe resources in that group. A security list, on the other hand,includes rules that apply to all the resources in any subnet that usesthe security list. A VCN may be provided with a default security listwith default security rules. DHCP options configured for a VCN provideconfiguration information that is automatically provided to theinstances in the VCN when the instances boot up.

In certain embodiments, the configuration information for a VCN isdetermined and stored by a VCN Control Plane. The configurationinformation for a VCN may include, for example, information about: theaddress range associated with the VCN, subnets within the VCN andassociated information, one or more VRs associated with the VCN, computeinstances in the VCN and associated VNICs, NVDs executing the variousvirtualization network functions (e.g., VNICs, VRs, gateways) associatedwith the VCN, state information for the VCN, and other VCN-relatedinformation. In certain embodiments, a VCN Distribution Servicepublishes the configuration information stored by the VCN Control Plane,or portions thereof, to the NVDs. The distributed information may beused to update information (e.g., forwarding tables, routing tables,etc.) stored and used by the NVDs to forward packets to and from thecompute instances in the VCN.

In certain embodiments, the creation of VCNs and subnets are handled bya VCN Control Plane (CP) and the launching of compute instances ishandled by a Compute Control Plane. The Compute Control Plane isresponsible for allocating the physical resources for the computeinstance and then calls the VCN Control Plane to create and attach VNICsto the compute instance. The VCN CP also sends VCN data mappings to theVCN data plane that is configured to perform packet forwarding androuting functions.

A customer may create one or more VCNs using resources hosted by CSPI. Acompute instance deployed on a customer VCN may communicate withdifferent endpoints. These endpoints can include endpoints that arehosted by CSPI and endpoints outside CSPI.

Various different architectures for implementing cloud-based serviceusing CSPI are depicted in FIGS. 15, 16, 17, 18, and 19 , and aredescribed below. FIG. 15 is a high level diagram of a distributedenvironment 1500 showing an overlay or customer VCN hosted by CSPIaccording to certain embodiments. The distributed environment depictedin FIG. 15 includes multiple components in the overlay network.Distributed environment 1500 depicted in FIG. 15 is merely an exampleand is not intended to unduly limit the scope of claimed embodiments.Many variations, alternatives, and modifications are possible. Forexample, in some implementations, the distributed environment depictedin FIG. 15 may have more or fewer systems or components than those shownin FIG. 1 , may combine two or more systems, or may have a differentconfiguration or arrangement of systems.

As shown in the example depicted in FIG. 15 , distributed environment1500 comprises CSPI 1501 that provides services and resources thatcustomers can subscribe to and use to build their virtual cloud networks(VCNs). In certain embodiments, CSPI 1501 offers IaaS services tosubscribing customers. The data centers within CSPI 1501 may beorganized into one or more regions. One example region “Region US” 1502is shown in FIG. 15 . A customer has configured a customer VCN 1504 forregion 1502. The customer may deploy various compute instances on VCN1504, where the compute instances may include virtual machines or baremetal instances. Examples of instances include applications, database,load balancers, and the like.

In the embodiment depicted in FIG. 15 , customer VCN 1504 comprises twosubnets, namely, “Subnet-1” and “Subnet-2”, each subnet with its ownCIDR IP address range. In FIG. 15 , the overlay IP address range forSubnet-1 is 10.0/16 and the address range for Subnet-2 is 10.1/16. A VCNVirtual Router 1505 represents a logical gateway for the VCN thatenables communications between subnets of the VCN 1504, and with otherendpoints outside the VCN. VCN VR 1505 is configured to route trafficbetween VNICs in VCN 1504 and gateways associated with VCN 1504. VCN VR1505 provides a port for each subnet of VCN 1504. For example, VR 1505may provide a port with IP address 10.0.0.1 for Subnet-1 and a port withIP address 10.1.0.1 for Subnet-2.

Multiple compute instances may be deployed on each subnet, where thecompute instances can be virtual machine instances, and/or bare metalinstances. The compute instances in a subnet may be hosted by one ormore host machines within CSPI 1501. A compute instance participates ina subnet via a VNIC associated with the compute instance. For example,as shown in FIG. 15 , a compute instance C1 is part of Subnet-1 via aVNIC associated with the compute instance. Likewise, compute instance C2is part of Subnet-1 via a VNIC associated with C2. In a similar manner,multiple compute instances, which may be virtual machine instances orbare metal instances, may be part of Subnet-1. Via its associated VNIC,each compute instance is assigned a private overlay IP address and a MACaddress. For example, in FIG. 15 , compute instance C1 has an overlay IPaddress of 10.0.0.2 and a MAC address of M1, while compute instance C2has an private overlay IP address of 10.0.0.3 and a MAC address of M2.Each compute instance in Subnet-1, including compute instances C1 andC2, has a default route to VCN VR 1505 using IP address 10.0.0.1, whichis the IP address for a port of VCN VR 1505 for Subnet-1.

Subnet-2 can have multiple compute instances deployed on it, includingvirtual machine instances and/or bare metal instances. For example, asshown in FIG. 15 , compute instances D1 and D2 are part of Subnet-2 viaVNICs associated with the respective compute instances. In theembodiment depicted in FIG. 15 , compute instance D1 has an overlay IPaddress of 10.1.0.2 and a MAC address of MM1, while compute instance D2has an private overlay IP address of 10.1.0.3 and a MAC address of MM2.Each compute instance in Subnet-2, including compute instances D1 andD2, has a default route to VCN VR 1505 using IP address 10.1.0.1, whichis the IP address for a port of VCN VR 1505 for Subnet-2.

VCN A 1504 may also include one or more load balancers. For example, aload balancer may be provided for a subnet and may be configured to loadbalance traffic across multiple compute instances on the subnet. A loadbalancer may also be provided to load balance traffic across subnets inthe VCN.

A particular compute instance deployed on VCN 1504 can communicate withvarious different endpoints. These endpoints may include endpoints thatare hosted by CSPI 1600 and endpoints outside CSPI 1600. Endpoints thatare hosted by CSPI 1501 may include: an endpoint on the same subnet asthe particular compute instance (e.g., communications between twocompute instances in Subnet-1); an endpoint on a different subnet butwithin the same VCN (e.g., communication between a compute instance inSubnet-1 and a compute instance in Subnet-2); an endpoint in a differentVCN in the same region (e.g., communications between a compute instancein Subnet-1 and an endpoint in a VCN in the same region 1506 or 1510,communications between a compute instance in Subnet-1 and an endpoint inservice network 1510 in the same region); or an endpoint in a VCN in adifferent region (e.g., communications between a compute instance inSubnet-1 and an endpoint in a VCN in a different region 1508). A computeinstance in a subnet hosted by CSPI 1501 may also communicate withendpoints that are not hosted by CSPI 1501 (i.e., are outside CSPI1501). These outside endpoints include endpoints in the customer'son-premise network 1516, endpoints within other remote cloud hostednetworks 1518, public endpoints 1514 accessible via a public networksuch as the Internet, and other endpoints.

Communications between compute instances on the same subnet arefacilitated using VNICs associated with the source compute instance andthe destination compute instance. For example, compute instance C1 inSubnet-1 may want to send packets to compute instance C2 in Subnet-1.For a packet originating at a source compute instance and whosedestination is another compute instance in the same subnet, the packetis first processed by the VNIC associated with the source computeinstance. Processing performed by the VNIC associated with the sourcecompute instance can include determining destination information for thepacket from the packet headers, identifying any policies (e.g., securitylists) configured for the VNIC associated with the source computeinstance, determining a next hop for the packet, performing any packetencapsulation/decapsulation functions as needed, and thenforwarding/routing the packet to the next hop with the goal offacilitating communication of the packet to its intended destination.When the destination compute instance is in the same subnet as thesource compute instance, the VNIC associated with the source computeinstance is configured to identify the VNIC associated with thedestination compute instance and forward the packet to that VNIC forprocessing. The VNIC associated with the destination compute instance isthen executed and forwards the packet to the destination computeinstance.

For a packet to be communicated from a compute instance in a subnet toan endpoint in a different subnet in the same VCN, the communication isfacilitated by the VNICs associated with the source and destinationcompute instances and the VCN VR. For example, if compute instance C1 inSubnet-1 in FIG. 15 wants to send a packet to compute instance D1 inSubnet-2, the packet is first processed by the VNIC associated withcompute instance C1. The VNIC associated with compute instance C1 isconfigured to route the packet to the VCN VR 1505 using default route orport 10.0.0.1 of the VCN VR. VCN VR 1505 is configured to route thepacket to Subnet-2 using port 10.1.0.1. The packet is then received andprocessed by the VNIC associated with D1 and the VNIC forwards thepacket to compute instance D1.

For a packet to be communicated from a compute instance in VCN 1504 toan endpoint that is outside VCN 1504, the communication is facilitatedby the VNIC associated with the source compute instance, VCN VR 1505,and gateways associated with VCN 1504. One or more types of gateways maybe associated with VCN 1504. A gateway is an interface between a VCN andanother endpoint, where the another endpoint is outside the VCN. Agateway is a Layer-3/IP layer concept and enables a VCN to communicatewith endpoints outside the VCN. A gateway thus facilitates traffic flowbetween a VCN and other VCNs or networks. Various different types ofgateways may be configured for a VCN to facilitate different types ofcommunications with different types of endpoints. Depending upon thegateway, the communications may be over public networks (e.g., theInternet) or over private networks. Various communication protocols maybe used for these communications.

For example, compute instance C1 may want to communicate with anendpoint outside VCN 1504. The packet may be first processed by the VNICassociated with source compute instance C1. The VNIC processingdetermines that the destination for the packet is outside the Subnet-1of C1. The VNIC associated with C1 may forward the packet to VCN VR 1505for VCN 1504. VCN VR 1505 then processes the packet and as part of theprocessing, based upon the destination for the packet, determines aparticular gateway associated with VCN 1504 as the next hop for thepacket. VCN VR 1505 may then forward the packet to the particularidentified gateway. For example, if the destination is an endpointwithin the customer's on-premise network, then the packet may beforwarded by VCN VR 1505 to Dynamic Routing Gateway (DRG) gateway 1522configured for VCN 1504. The packet may then be forwarded from thegateway to a next hop to facilitate communication of the packet to itfinal intended destination.

Various different types of gateways may be configured for a VCN.Examples of gateways that may be configured for a VCN are depicted inFIG. 15 and described below. As shown in the embodiment depicted in FIG.15 , a Dynamic Routing Gateway (DRG) 1522 may be added to or beassociated with customer VCN 1504 and provides a path for privatenetwork traffic communication between customer VCN 1504 and anotherendpoint, where the another endpoint can be the customer's on-premisenetwork 1516, a VCN 1508 in a different region of CSPI 1501, or otherremote cloud networks 1518 not hosted by CSPI 1501. Customer on-premisenetwork 1516 may be a customer network or a customer data center builtusing the customer's resources. Access to customer on-premise network1516 is generally very restricted. For a customer that has both acustomer on-premise network 1516 and one or more VCNs 1504 deployed orhosted in the cloud by CSPI 1501, the customer may want their on-premisenetwork 1516 and their cloud-based VCN 1504 to be able to communicatewith each other. This enables a customer to build an extended hybridenvironment encompassing the customer's VCN 1504 hosted by CSPI 1501 andtheir on-premises network 1516. DRG 1522 enables this communication. Toenable such communications, a communication channel 1524 is set up whereone endpoint of the channel is in customer on-premise network 1516 andthe other endpoint is in CSPI 1501 and connected to customer VCN 1504.Communication channel 1524 can be over public communication networkssuch as the Internet or private communication networks. Variousdifferent communication protocols may be used such as IPsec VPNtechnology over a public communication network such as the Internet,Oracle's FastConnect technology that uses a private network instead of apublic network, and others. The device or equipment in customeron-premise network 1516 that forms one end point for communicationchannel 1524 is referred to as the customer premise equipment (CPE),such as CPE 1526 depicted in FIG. 15 . On the CSPI 1501 side, theendpoint may be a host machine executing DRG 1522.

In certain embodiments, a Remote Peering Connection (RPC) can be addedto a DRG, which allows a customer to peer one VCN with another VCN in adifferent region. Using such an RPC, customer VCN 1504 can use DRG 1522to connect with a VCN 1508 in another region. DRG 1522 may also be usedto communicate with other remote cloud networks 1518, not hosted by CSPI1501 such as a Microsoft Azure cloud, Amazon AWS cloud, and others.

As shown in FIG. 15 , an Internet Gateway (IGW) 1520 may be configuredfor customer VCN 1504 the enables a compute instance on VCN 1504 tocommunicate with public endpoints 1514 accessible over a public networksuch as the Internet. IGW 15120 is a gateway that connects a VCN to apublic network such as the Internet. IGW 1520 enables a public subnet(where the resources in the public subnet have public overlay IPaddresses) within a VCN, such as VCN 1504, direct access to publicendpoints 1512 on a public network 1514 such as the Internet. Using IGW1520, connections can be initiated from a subnet within VCN 1504 or fromthe Internet.

A Network Address Translation (NAT) gateway 1528 can be configured forcustomer's VCN 1504 and enables cloud resources in the customer's VCN,which do not have dedicated public overlay IP addresses, access to theInternet and it does so without exposing those resources to directincoming Internet connections (e.g., L4-L7 connections). This enables aprivate subnet within a VCN, such as private Subnet-1 in VCN 1504, withprivate access to public endpoints on the Internet. In NAT gateways,connections can be initiated only from the private subnet to the publicInternet and not from the Internet to the private subnet.

In certain embodiments, a Service Gateway (SGW) 1526 can be configuredfor customer VCN 1504 and provides a path for private network trafficbetween VCN 1504 and supported services endpoints in a service network1510. In certain embodiments, service network 1510 may be provided bythe CSP and may provide various services. An example of such a servicenetwork is Oracle's Services Network, which provides various servicesthat can be used by customers. For example, a compute instance (e.g., adatabase system) in a private subnet of customer VCN 1504 can back updata to a service endpoint (e.g., Object Storage) without needing publicIP addresses or access to the Internet. In certain embodiments, a VCNcan have only one SGW, and connections can only be initiated from asubnet within the VCN and not from service network 1510. If a VCN ispeered with another, resources in the other VCN typically cannot accessthe SGW. Resources in on-premises networks that are connected to a VCNwith FastConnect or VPN Connect can also use the service gatewayconfigured for that VCN.

In certain implementations, SGW 1526 uses the concept of a serviceClassless Inter-Domain Routing (CIDR) label, which is a string thatrepresents all the regional public IP address ranges for the service orgroup of services of interest. The customer uses the service CIDR labelwhen they configure the SGW and related route rules to control trafficto the service. The customer can optionally utilize it when configuringsecurity rules without needing to adjust them if the service's public IPaddresses change in the future.

A Local Peering Gateway (LPG) 1532 is a gateway that can be added tocustomer VCN 1504 and enables VCN 1504 to peer with another VCN in thesame region. Peering means that the VCNs communicate using private IPaddresses, without the traffic traversing a public network such as theInternet or without routing the traffic through the customer'son-premises network 1516. In preferred embodiments, a VCN has a separateLPG for each peering it establishes. Local Peering or VCN Peering is acommon practice used to establish network connectivity between differentapplications or infrastructure management functions.

Service providers, such as providers of services in service network1510, may provide access to services using different access models.According to a public access model, services may be exposed as publicendpoints that are publicly accessible by compute instance in a customerVCN via a public network such as the Internet and or may be privatelyaccessible via SGW 1526. According to a specific private access model,services are made accessible as private IP endpoints in a private subnetin the customer's VCN. This is referred to as a Private Endpoint (PE)access and enables a service provider to expose their service as aninstance in the customer's private network. A Private Endpoint resourcerepresents a service within the customer's VCN. Each PE manifests as aVNIC (referred to as a PE-VNIC, with one or more private IPs) in asubnet chosen by the customer in the customer's VCN. A PE thus providesa way to present a service within a private customer VCN subnet using aVNIC. Since the endpoint is exposed as a VNIC, all the featuresassociates with a VNIC such as routing rules, security lists, etc., arenow available for the PE VNIC.

A service provider can register their service to enable access through aPE. The provider can associate policies with the service that restrictsthe service's visibility to the customer tenancies. A provider canregister multiple services under a single virtual IP address (VIP),especially for multi-tenant services. There may be multiple such privateendpoints (in multiple VCNs) that represent the same service.

Compute instances in the private subnet can then use the PE VNIC'sprivate IP address or the service DNS name to access the service.Compute instances in the customer VCN can access the service by sendingtraffic to the private IP address of the PE in the customer VCN. APrivate Access Gateway (PAGW) 1530 is a gateway resource that can beattached to a service provider VCN (e.g., a VCN in service network 1510)that acts as an ingress/egress point for all traffic from/to customersubnet private endpoints. PAGW 1530 enables a provider to scale thenumber of PE connections without utilizing its internal IP addressresources. A provider needs only configure one PAGW for any number ofservices registered in a single VCN. Providers can represent a serviceas a private endpoint in multiple VCNs of one or more customers. Fromthe customer's perspective, the PE VNIC, which, instead of beingattached to a customer's instance, appears attached to the service withwhich the customer wishes to interact. The traffic destined to theprivate endpoint is routed via PAGW 1530 to the service. These arereferred to as customer-to-service private connections (C2Sconnections).

The PE concept can also be used to extend the private access for theservice to customer's on-premises networks and data centers, by allowingthe traffic to flow through FastConnect/IPsec links and the privateendpoint in the customer VCN. Private access for the service can also beextended to the customer's peered VCNs, by allowing the traffic to flowbetween LPG 1532 and the PE in the customer's VCN.

A customer can control routing in a VCN at the subnet level, so thecustomer can specify which subnets in the customer's VCN, such as VCN1504, use each gateway. A VCN's route tables are used to decide iftraffic is allowed out of a VCN through a particular gateway. Forexample, in a particular instance, a route table for a public subnetwithin customer VCN 1504 may send non-local traffic through IGW 1520.The route table for a private subnet within the same customer VCN 1504may send traffic destined for CSP services through SGW 1526. Allremaining traffic may be sent via the NAT gateway 1528. Route tablesonly control traffic going out of a VCN.

Security lists associated with a VCN are used to control traffic thatcomes into a VCN via a gateway via inbound connections. All resources ina subnet use the same route table and security lists. Security lists maybe used to control specific types of traffic allowed in and out ofinstances in a subnet of a VCN. Security list rules may comprise ingress(inbound) and egress (outbound) rules. For example, an ingress rule mayspecify an allowed source address range, while an egress rule mayspecify an allowed destination address range. Security rules may specifya particular protocol (e.g., TCP, ICMP), a particular port (e.g., 22 forSSH, 3389 for Windows RDP), etc. In certain implementations, aninstance's operating system may enforce its own firewall rules that arealigned with the security list rules. Rules may be stateful (e.g., aconnection is tracked and the response is automatically allowed withoutan explicit security list rule for the response traffic) or stateless.

Access from a customer VCN (i.e., by a resource or compute instancedeployed on VCN 1504) can be categorized as public access, privateaccess, or dedicated access. Public access refers to an access modelwhere a public IP address or a NAT is used to access a public endpoint.Private access enables customer workloads in VCN 1504 with private IPaddresses (e.g., resources in a private subnet) to access serviceswithout traversing a public network such as the Internet. In certainembodiments, CSPI 1501 enables customer VCN workloads with private IPaddresses to access the (public service endpoints of) services using aservice gateway. A service gateway thus offers a private access model byestablishing a virtual link between the customer's VCN and the service'spublic endpoint residing outside the customer's private network.

Additionally, CSPI may offer dedicated public access using technologiessuch as FastConnect public peering where customer on-premises instancescan access one or more services in a customer VCN using a FastConnectconnection and without traversing a public network such as the Internet.CSPI also may also offer dedicated private access using FastConnectprivate peering where customer on-premises instances with private IPaddresses can access the customer's VCN workloads using a FastConnectconnection. FastConnect is a network connectivity alternative to usingthe public Internet to connect a customer's on-premise network to CSPIand its services. FastConnect provides an easy, elastic, and economicalway to create a dedicated and private connection with higher bandwidthoptions and a more reliable and consistent networking experience whencompared to Internet-based connections.

FIG. 15 and the accompanying description above describes variousvirtualized components in an example virtual network. As describedabove, the virtual network is built on the underlying physical orsubstrate network. FIG. 16 depicts a simplified architectural diagram ofthe physical components in the physical network within CSPI 1600 thatprovide the underlay for the virtual network according to certainembodiments. As shown, CSPI 1600 provides a distributed environmentcomprising components and resources (e.g., compute, memory, andnetworking resources) provided by a cloud service provider (CSP). Thesecomponents and resources are used to provide cloud services (e.g., IaaSservices) to subscribing customers, i.e., customers that have subscribedto one or more services provided by the CSP. Based upon the servicessubscribed to by a customer, a subset of resources (e.g., compute,memory, and networking resources) of CSPI 1600 are provisioned for thecustomer. Customers can then build their own cloud-based (i.e.,CSPI-hosted) customizable and private virtual networks using physicalcompute, memory, and networking resources provided by CSPI 1600. Aspreviously indicated, these customer networks are referred to as virtualcloud networks (VCNs). A customer can deploy one or more customerresources, such as compute instances, on these customer VCNs. Computeinstances can be in the form of virtual machines, bare metal instances,and the like. CSPI 1600 provides infrastructure and a set ofcomplementary cloud services that enable customers to build and run awide range of applications and services in a highly available hostedenvironment.

In the example embodiment depicted in FIG. 16 , the physical componentsof CSPI 1600 include one or more physical host machines or physicalservers (e.g., 1602, 1606, 1608), network virtualization devices (NVDs)(e.g., 1610, 1612), top-of-rack (TOR) switches (e.g., 1614, 1616), and aphysical network (e.g., 1618), and switches in physical network 1618.The physical host machines or servers may host and execute variouscompute instances that participate in one or more subnets of a VCN. Thecompute instances may include virtual machine instances, and bare metalinstances. For example, the various compute instances depicted in FIG.15 may be hosted by the physical host machines depicted in FIG. 16 . Thevirtual machine compute instances in a VCN may be executed by one hostmachine or by multiple different host machines. The physical hostmachines may also host virtual host machines, container-based hosts orfunctions, and the like. The VNICs and VCN VR depicted in FIG. 15 may beexecuted by the NVDs depicted in FIG. 16 . The gateways depicted in FIG.15 may be executed by the host machines and/or by the NVDs depicted inFIG. 16 .

The host machines or servers may execute a hypervisor (also referred toas a virtual machine monitor or VMM) that creates and enables avirtualized environment on the host machines. The virtualization orvirtualized environment facilitates cloud-based computing. One or morecompute instances may be created, executed, and managed on a hostmachine by a hypervisor on that host machine. The hypervisor on a hostmachine enables the physical computing resources of the host machine(e.g., compute, memory, and networking resources) to be shared betweenthe various compute instances executed by the host machine.

For example, as depicted in FIG. 16 , host machines 1602 and 1608execute hypervisors 1660 and 1666, respectively. These hypervisors maybe implemented using software, firmware, or hardware, or combinationsthereof. Typically, a hypervisor is a process or a software layer thatsits on top of the host machine's operating system (OS), which in turnexecutes on the hardware processors of the host machine. The hypervisorprovides a virtualized environment by enabling the physical computingresources (e.g., processing resources such as processors/cores, memoryresources, networking resources) of the host machine to be shared amongthe various virtual machine compute instances executed by the hostmachine. For example, in FIG. 16 , hypervisor 1660 may sit on top of theOS of host machine 1602 and enables the computing resources (e.g.,processing, memory, and networking resources) of host machine 1602 to beshared between compute instances (e.g., virtual machines) executed byhost machine 1602. A virtual machine can have its own operating system(referred to as a guest operating system), which may be the same as ordifferent from the OS of the host machine. The operating system of avirtual machine executed by a host machine may be the same as ordifferent from the operating system of another virtual machine executedby the same host machine. A hypervisor thus enables multiple operatingsystems to be executed alongside each other while sharing the samecomputing resources of the host machine. The host machines depicted inFIG. 16 may have the same or different types of hypervisors.

A compute instance can be a virtual machine instance or a bare metalinstance. In FIG. 16 , compute instances 1668 on host machine 1602 and1674 on host machine 1608 are examples of virtual machine instances.Host machine 1606 is an example of a bare metal instance that isprovided to a customer.

In certain instances, an entire host machine may be provisioned to asingle customer, and all of the one or more compute instances (eithervirtual machines or bare metal instance) hosted by that host machinebelong to that same customer. In other instances, a host machine may beshared between multiple customers (i.e., multiple tenants). In such amulti-tenancy scenario, a host machine may host virtual machine computeinstances belonging to different customers. These compute instances maybe members of different VCNs of different customers. In certainembodiments, a bare metal compute instance is hosted by a bare metalserver without a hypervisor. When a bare metal compute instance isprovisioned, a single customer or tenant maintains control of thephysical CPU, memory, and network interfaces of the host machine hostingthe bare metal instance and the host machine is not shared with othercustomers or tenants.

As previously described, each compute instance that is part of a VCN isassociated with a VNIC that enables the compute instance to become amember of a subnet of the VCN. The VNIC associated with a computeinstance facilitates the communication of packets or frames to and fromthe compute instance. A VNIC is associated with a compute instance whenthe compute instance is created. In certain embodiments, for a computeinstance executed by a host machine, the VNIC associated with thatcompute instance is executed by an NVD connected to the host machine.For example, in FIG. 16 , host machine 1602 executes a virtual machinecompute instance 1668 that is associated with VNIC 1676, and VNIC 1676is executed by NVD 1610 connected to host machine 1602. As anotherexample, bare metal instance 1672 hosted by host machine 1606 isassociated with VNIC 1680 that is executed by NVD 1612 connected to hostmachine 1606. As yet another example, VNIC 1684 is associated withcompute instance 1674 executed by host machine 1608, and VNIC 1684 isexecuted by NVD 1612 connected to host machine 1608.

For compute instances hosted by a host machine, an NVD connected to thathost machine also executes VCN VRs corresponding to VCNs of which thecompute instances are members. For example, in the embodiment depictedin FIG. 16 , NVD 1610 executes VCN VR 1677 corresponding to the VCN ofwhich compute instance 1668 is a member. NVD 1612 may also execute oneor more VCN VRs 1683 corresponding to VCNs corresponding to the computeinstances hosted by host machines 1606 and 1608.

A host machine may include one or more network interface cards (NIC)that enable the host machine to be connected to other devices. A NIC ona host machine may provide one or more ports (or interfaces) that enablethe host machine to be communicatively connected to another device. Forexample, a host machine may be connected to an NVD using one or moreports (or interfaces) provided on the host machine and on the NVD. Ahost machine may also be connected to other devices such as another hostmachine.

For example, in FIG. 16 , host machine 1602 is connected to NVD 1610using link 1620 that extends between a port 1634 provided by a NIC 1632of host machine 1602 and between a port 1636 of NVD 1610. Host machine1606 is connected to NVD 1612 using link 1624 that extends between aport 1646 provided by a NIC 1644 of host machine 1606 and between a port1648 of NVD 1612. Host machine 1608 is connected to NVD 1612 using link1626 that extends between a port 1652 provided by a NIC 1650 of hostmachine 1608 and between a port 1654 of NVD 1612.

The NVDs are in turn connected via communication links totop-of-the-rack (TOR) switches, which are connected to physical network1618 (also referred to as the switch fabric). In certain embodiments,the links between a host machine and an NVD, and between an NVD and aTOR switch are Ethernet links. For example, in FIG. 16 , NVDs 1610 and1612 are connected to TOR switches 1614 and 1616, respectively, usinglinks 1628 and 1630. In certain embodiments, the links 1620, 1624, 1626,1628, and 1630 are Ethernet links. The collection of host machines andNVDs that are connected to a TOR is sometimes referred to as a rack.

Physical network 1618 provides a communication fabric that enables TORswitches to communicate with each other. Physical network 1618 can be amulti-tiered network. In certain implementations, physical network 1618is a multi-tiered Clos network of switches, with TOR switches 1614 and1616 representing the leaf level nodes of the multi-tiered andmulti-node physical switching network 1618. Different Clos networkconfigurations are possible including but not limited to a 2-tiernetwork, a 3-tier network, a 4-tier network, a 5-tier network, and ingeneral a “n”-tiered network. An example of a Clos network is depictedin FIG. 19 and described below.

Various different connection configurations are possible between hostmachines and NVDs such as one-to-one configuration, many-to-oneconfiguration, one-to-many configuration, and others. In a one-to-oneconfiguration implementation, each host machine is connected to its ownseparate NVD. For example, in FIG. 16 , host machine 1602 is connectedto NVD 1610 via NIC 1632 of host machine 1602. In a many-to-oneconfiguration, multiple host machines are connected to one NVD. Forexample, in FIG. 16 , host machines 1606 and 1608 are connected to thesame NVD 1612 via NICs 1644 and 1650, respectively.

In a one-to-many configuration, one host machine is connected tomultiple NVDs. FIG. 17 shows an example within CSPI 1700 where a hostmachine is connected to multiple NVDs. As shown in FIG. 17 , hostmachine 1702 comprises a network interface card (NIC) 1704 that includesmultiple ports 1706 and 1708. Host machine 1700 is connected to a firstNVD 1710 via port 1706 and link 1720, and connected to a second NVD 1712via port 1708 and link 1722. Ports 1706 and 1708 may be Ethernet portsand the links 1720 and 1722 between host machine 1702 and NVDs 1710 and1712 may be Ethernet links. NVD 1710 is in turn connected to a first TORswitch 1714 and NVD 1712 is connected to a second TOR switch 1716. Thelinks between NVDs 1710 and 1712, and TOR switches 1714 and 1716 may beEthernet links. TOR switches 1714 and 1716 represent the Tier-0switching devices in multi-tiered physical network 1718.

The arrangement depicted in FIG. 17 provides two separate physicalnetwork paths to and from physical switch network 1718 to host machine1702: a first path traversing TOR switch 1714 to NVD 1710 to hostmachine 1702, and a second path traversing TOR switch 1716 to NVD 1712to host machine 1702. The separate paths provide for enhancedavailability (referred to as high availability) of host machine 1702. Ifthere are problems in one of the paths (e.g., a link in one of the pathsgoes down) or devices (e.g., a particular NVD is not functioning), thenthe other path may be used for communications to/from host machine 1702.

In the configuration depicted in FIG. 17 , the host machine is connectedto two different NVDs using two different ports provided by a NIC of thehost machine. In other embodiments, a host machine may include multipleNICs that enable connectivity of the host machine to multiple NVDs.

Referring back to FIG. 16 , an NVD is a physical device or componentthat performs one or more network and/or storage virtualizationfunctions. An NVD may be any device with one or more processing units(e.g., CPUs, Network Processing Units (NPUs), FPGAs, packet processingpipelines, etc.), memory including cache, and ports. The variousvirtualization functions may be performed by software/firmware executedby the one or more processing units of the NVD.

An NVD may be implemented in various different forms. For example, incertain embodiments, an NVD is implemented as an interface card referredto as a smartNIC or an intelligent NIC with an embedded processoronboard. A smartNIC is a separate device from the NICs on the hostmachines. In FIG. 16 , the NVDs 1610 and 1612 may be implemented assmartNICs that are connected to host machines 1602, and host machines1606 and 1608, respectively.

A smartNIC is however just one example of an NVD implementation. Variousother implementations are possible. For example, in some otherimplementations, an NVD or one or more functions performed by the NVDmay be incorporated into or performed by one or more host machines, oneor more TOR switches, and other components of CSPI 1600. For example, anNVD may be embodied in a host machine where the functions performed byan NVD are performed by the host machine. As another example, an NVD maybe part of a TOR switch or a TOR switch may be configured to performfunctions performed by an NVD that enables the TOR switch to performvarious complex packet transformations that are used for a public cloud.A TOR that performs the functions of an NVD is sometimes referred to asa smart TOR. In yet other implementations, where virtual machines (VMs)instances, but not bare metal (BM) instances, are offered to customers,functions performed by an NVD may be implemented inside a hypervisor ofthe host machine. In some other implementations, some of the functionsof the NVD may be offloaded to a centralized service running on a fleetof host machines.

In certain embodiments, such as when implemented as a smartNIC as shownin FIG. 16 , an NVD may comprise multiple physical ports that enable itto be connected to one or more host machines and to one or more TORswitches. A port on an NVD can be classified as a host-facing port (alsoreferred to as a “south port”) or a network-facing or TOR-facing port(also referred to as a “north port”). A host-facing port of an NVD is aport that is used to connect the NVD to a host machine. Examples ofhost-facing ports in FIG. 16 include port 1636 on NVD 1610, and ports1648 and 1654 on NVD 1612. A network-facing port of an NVD is a portthat is used to connect the NVD to a TOR switch. Examples ofnetwork-facing ports in FIG. 16 include port 1656 on NVD 1610, and port1658 on NVD 1612. As shown in FIG. 16 , NVD 1610 is connected to TORswitch 1614 using link 1628 that extends from port 1656 of NVD 1610 tothe TOR switch 1614. Likewise, NVD 1612 is connected to TOR switch 1616using link 1630 that extends from port 1658 of NVD 1612 to the TORswitch 1616.

An NVD receives packets and frames from a host machine (e.g., packetsand frames generated by a compute instance hosted by the host machine)via a host-facing port and, after performing the necessary packetprocessing, may forward the packets and frames to a TOR switch via anetwork-facing port of the NVD. An NVD may receive packets and framesfrom a TOR switch via a network-facing port of the NVD and, afterperforming the necessary packet processing, may forward the packets andframes to a host machine via a host-facing port of the NVD.

In certain embodiments, there may be multiple ports and associated linksbetween an NVD and a TOR switch. These ports and links may be aggregatedto form a link aggregator group of multiple ports or links (referred toas a LAG). Link aggregation allows multiple physical links between twoend-points (e.g., between an NVD and a TOR switch) to be treated as asingle logical link. All the physical links in a given LAG may operatein full-duplex mode at the same speed. LAGs help increase the bandwidthand reliability of the connection between two endpoints. If one of thephysical links in the LAG goes down, traffic is dynamically andtransparently reassigned to one of the other physical links in the LAG.The aggregated physical links deliver higher bandwidth than eachindividual link. The multiple ports associated with a LAG are treated asa single logical port. Traffic can be load-balanced across the multiplephysical links of a LAG. One or more LAGs may be configured between twoendpoints. The two endpoints may be between an NVD and a TOR switch,between a host machine and an NVD, and the like.

An NVD implements or performs network virtualization functions. Thesefunctions are performed by software/firmware executed by the NVD.Examples of network virtualization functions include without limitation:packet encapsulation and de-capsulation functions; functions forcreating a VCN network; functions for implementing network policies suchas VCN security list (firewall) functionality; functions that facilitatethe routing and forwarding of packets to and from compute instances in aVCN; and the like. In certain embodiments, upon receiving a packet, anNVD is configured to execute a packet processing pipeline for processingthe packet and determining how the packet is to be forwarded or routed.As part of this packet processing pipeline, the NVD may execute one ormore virtual functions associated with the overlay network such asexecuting VNICs associated with cis in the VCN, executing a VirtualRouter (VR) associated with the VCN, the encapsulation and decapsulationof packets to facilitate forwarding or routing in the virtual network,execution of certain gateways (e.g., the Local Peering Gateway), theimplementation of Security Lists, Network Security Groups, networkaddress translation (NAT) functionality (e.g., the translation of PublicIP to Private IP on a host by host basis), throttling functions, andother functions.

In certain embodiments, the packet processing data path in an NVD maycomprise multiple packet pipelines, each composed of a series of packettransformation stages. In certain implementations, upon receiving apacket, the packet is parsed and classified to a single pipeline. Thepacket is then processed in a linear fashion, one stage after another,until the packet is either dropped or sent out over an interface of theNVD. These stages provide basic functional packet processing buildingblocks (e.g., validating headers, enforcing throttle, inserting newLayer-2 headers, enforcing L4 firewall, VCN encapsulation/decapsulation,etc.) so that new pipelines can be constructed by composing existingstages, and new functionality can be added by creating new stages andinserting them into existing pipelines.

An NVD may perform both control plane and data plane functionscorresponding to a control plane and a data plane of a VCN. The controlplane functions include functions used for configuring a network (e.g.,setting up routes and route tables, configuring VNICs, etc.) thatcontrols how data is to be forwarded. In certain embodiments, a VCNControl Plane is provided that computes all the overlay-to-substratemappings centrally and publishes them to the NVDs and to the virtualnetwork edge devices such as various gateways such as the DRG, the SGW,the IGW, etc. Firewall rules may also be published using the samemechanism. In certain embodiments, an NVD only gets the mappings thatare relevant for that NVD. The data plane functions include functionsfor the actual routing/forwarding of a packet based upon configurationset up using control plane. A VCN data plane is implemented byencapsulating the customer's network packets before they traverse thesubstrate network. The encapsulation/decapsulation functionality isimplemented on the NVDs. In certain embodiments, an NVD is configured tointercept all network packets in and out of host machines and performnetwork virtualization functions.

As indicated above, an NVD executes various virtualization functionsincluding VNICs and VCN VRs. An NVD may execute VNICs associated withthe compute instances hosted by one or more host machines connected tothe VNIC. For example, as depicted in FIG. 16 , NVD 1610 executes thefunctionality for VNIC 1676 that is associated with compute instance1668 hosted by host machine 1602 connected to NVD 1610. As anotherexample, NVD 1612 executes VNIC 1680 that is associated with bare metalcompute instance 1672 hosted by host machine 1606, and executes VNIC1684 that is associated with compute instance 1674 hosted by hostmachine 1608. A host machine may host compute instances belonging todifferent VCNs, which belong to different customers, and the NVDconnected to the host machine may execute the VNICs (i.e., executeVNICs-relate functionality) corresponding to the compute instances.

An NVD also executes VCN Virtual Routers corresponding to the VCNs ofthe compute instances. For example, in the embodiment depicted in FIG.16 , NVD 1610 executes VCN VR 1677 corresponding to the VCN to whichcompute instance 1668 belongs. NVD 1612 executes one or more VCN VRs1683 corresponding to one or more VCNs to which compute instances hostedby host machines 1606 and 1608 belong. In certain embodiments, the VCNVR corresponding to that VCN is executed by all the NVDs connected tohost machines that host at least one compute instance belonging to thatVCN. If a host machine hosts compute instances belonging to differentVCNs, an NVD connected to that host machine may execute VCN VRscorresponding to those different VCNs.

In addition to VNICs and VCN VRs, an NVD may execute various software(e.g., daemons) and include one or more hardware components thatfacilitate the various network virtualization functions performed by theNVD. For purposes of simplicity, these various components are groupedtogether as “packet processing components” shown in FIG. 16 . Forexample, NVD 1610 comprises packet processing components 1686 and NVD1612 comprises packet processing components 1688. For example, thepacket processing components for an NVD may include a packet processorthat is configured to interact with the NVD's ports and hardwareinterfaces to monitor all packets received by and communicated using theNVD and store network information. The network information may, forexample, include network flow information identifying different networkflows handled by the NVD and per flow information (e.g., per flowstatistics). In certain embodiments, network flows information may bestored on a per VNIC basis. The packet processor may performpacket-by-packet manipulations as well as implement stateful NAT and L4firewall (FW). As another example, the packet processing components mayinclude a replication agent that is configured to replicate informationstored by the NVD to one or more different replication target stores. Asyet another example, the packet processing components may include alogging agent that is configured to perform logging functions for theNVD. The packet processing components may also include software formonitoring the performance and health of the NVD and, also possibly ofmonitoring the state and health of other components connected to theNVD.

FIG. 15 shows the components of an example virtual or overlay networkincluding a VCN, subnets within the VCN, compute instances deployed onsubnets, VNICs associated with the compute instances, a VR for a VCN,and a set of gateways configured for the VCN. The overlay componentsdepicted in FIG. 15 may be executed or hosted by one or more of thephysical components depicted in FIG. 16 . For example, the computeinstances in a VCN may be executed or hosted by one or more hostmachines depicted in FIG. 16 . For a compute instance hosted by a hostmachine, the VNIC associated with that compute instance is typicallyexecuted by an NVD connected to that host machine (i.e., the VNICfunctionality is provided by the NVD connected to that host machine).The VCN VR function for a VCN is executed by all the NVDs that areconnected to host machines hosting or executing the compute instancesthat are part of that VCN. The gateways associated with a VCN may beexecuted by one or more different types of NVDs. For example, certaingateways may be executed by smartNICs, while others may be executed byone or more host machines or other implementations of NVDs.

As described above, a compute instance in a customer VCN may communicatewith various different endpoints, where the endpoints can be within thesame subnet as the source compute instance, in a different subnet butwithin the same VCN as the source compute instance, or with an endpointthat is outside the VCN of the source compute instance. Thesecommunications are facilitated using VNICs associated with the computeinstances, the VCN VRs, and the gateways associated with the VCNs.

For communications between two compute instances on the same subnet in aVCN, the communication is facilitated using VNICs associated with thesource and destination compute instances. The source and destinationcompute instances may be hosted by the same host machine or by differenthost machines. A packet originating from a source compute instance maybe forwarded from a host machine hosting the source compute instance toan NVD connected to that host machine. On the NVD, the packet isprocessed using a packet processing pipeline, which can includeexecution of the VNIC associated with the source compute instance. Sincethe destination endpoint for the packet is within the same subnet,execution of the VNIC associated with the source compute instanceresults in the packet being forwarded to an NVD executing the VNICassociated with the destination compute instance, which then processesand forwards the packet to the destination compute instance. The VNICsassociated with the source and destination compute instances may beexecuted on the same NVD (e.g., when both the source and destinationcompute instances are hosted by the same host machine) or on differentNVDs (e.g., when the source and destination compute instances are hostedby different host machines connected to different NVDs). The VNICs mayuse routing/forwarding tables stored by the NVD to determine the nexthop for the packet.

For a packet to be communicated from a compute instance in a subnet toan endpoint in a different subnet in the same VCN, the packetoriginating from the source compute instance is communicated from thehost machine hosting the source compute instance to the NVD connected tothat host machine. On the NVD, the packet is processed using a packetprocessing pipeline, which can include execution of one or more VNICs,and the VR associated with the VCN. For example, as part of the packetprocessing pipeline, the NVD executes or invokes functionalitycorresponding to the VNIC (also referred to as executes the VNIC)associated with source compute instance. The functionality performed bythe VNIC may include looking at the VLAN tag on the packet. Since thepacket's destination is outside the subnet, the VCN VR functionality isnext invoked and executed by the NVD. The VCN VR then routes the packetto the NVD executing the VNIC associated with the destination computeinstance. The VNIC associated with the destination compute instance thenprocesses the packet and forwards the packet to the destination computeinstance. The VNICs associated with the source and destination computeinstances may be executed on the same NVD (e.g., when both the sourceand destination compute instances are hosted by the same host machine)or on different NVDs (e.g., when the source and destination computeinstances are hosted by different host machines connected to differentNVDs).

If the destination for the packet is outside the VCN of the sourcecompute instance, then the packet originating from the source computeinstance is communicated from the host machine hosting the sourcecompute instance to the NVD connected to that host machine. The NVDexecutes the VNIC associated with the source compute instance. Since thedestination end point of the packet is outside the VCN, the packet isthen processed by the VCN VR for that VCN. The NVD invokes the VCN VRfunctionality, which may result in the packet being forwarded to an NVDexecuting the appropriate gateway associated with the VCN. For example,if the destination is an endpoint within the customer's on-premisenetwork, then the packet may be forwarded by the VCN VR to the NVDexecuting the DRG gateway configured for the VCN. The VCN VR may beexecuted on the same NVD as the NVD executing the VNIC associated withthe source compute instance or by a different NVD. The gateway may beexecuted by an NVD, which may be a smartNIC, a host machine, or otherNVD implementation. The packet is then processed by the gateway andforwarded to a next hop that facilitates communication of the packet toits intended destination endpoint. For example, in the embodimentdepicted in FIG. 16 , a packet originating from compute instance 1668may be communicated from host machine 1602 to NVD 1610 over link 1620(using NIC 1632). On NVD 1610, VNIC 1676 is invoked since it is the VNICassociated with source compute instance 1668. VNIC 1676 is configured toexamine the encapsulated information in the packet, and determine a nexthop for forwarding the packet with the goal of facilitatingcommunication of the packet to its intended destination endpoint, andthen forward the packet to the determined next hop.

A compute instance deployed on a VCN can communicate with variousdifferent endpoints. These endpoints may include endpoints that arehosted by CSPI 1600 and endpoints outside CSPI 1600. Endpoints hosted byCSPI 1600 may include instances in the same VCN or other VCNs, which maybe the customer's VCNs, or VCNs not belonging to the customer.Communications between endpoints hosted by CSPI 1600 may be performedover physical network 1618. A compute instance may also communicate withendpoints that are not hosted by CSPI 1600, or are outside CSPI 1600.Examples of these endpoints include endpoints within a customer'son-premise network or data center, or public endpoints accessible over apublic network such as the Internet. Communications with endpointsoutside CSPI 1600 may be performed over public networks (e.g., theInternet) (not shown in FIG. 16 ) or private networks (not shown in FIG.16 ) using various communication protocols.

The architecture of CSPI 1600 depicted in FIG. 16 is merely an exampleand is not intended to be limiting. Variations, alternatives, andmodifications are possible in alternative embodiments. For example, insome implementations, CSPI 1600 may have more or fewer systems orcomponents than those shown in FIG. 16 , may combine two or moresystems, or may have a different configuration or arrangement ofsystems. The systems, subsystems, and other components depicted in FIG.16 may be implemented in software (e.g., code, instructions, program)executed by one or more processing units (e.g., processors, cores) ofthe respective systems, using hardware, or combinations thereof. Thesoftware may be stored on a non-transitory storage medium (e.g., on amemory device).

FIG. 18 depicts connectivity between a host machine and an NVD forproviding I/O virtualization for supporting multitenancy according tocertain embodiments. As depicted in FIG. 18 , host machine 1802 executesa hypervisor 1804 that provides a virtualized environment. Host machine1802 executes two virtual machine instances, VM1 1806 belonging tocustomer/tenant #1 and VM2 1808 belonging to customer/tenant #2. Hostmachine 1802 comprises a physical NIC 1810 that is connected to an NVD1812 via link 1814. Each of the compute instances is attached to a VNICthat is executed by NVD 1812. In the embodiment in FIG. 18 , VM1 1806 isattached to VNIC-VM1 1820 and VM2 1808 is attached to VNIC-VM2 1822.

As shown in FIG. 18 , NIC 1810 comprises two logical NICs, logical NIC A1816 and logical NIC B 1818. Each virtual machine is attached to andconfigured to work with its own logical NIC. For example, VM1 1806 isattached to logical NIC A 1816 and VM2 1808 is attached to logical NIC B1818. Even though host machine 1802 comprises only one physical NIC 1810that is shared by the multiple tenants, due to the logical NICs, eachtenant's virtual machine believes they have their own host machine andNIC.

In certain embodiments, each logical NIC is assigned its own VLAN ID.Thus, a specific VLAN ID is assigned to logical NIC A 1816 for Tenant #1and a separate VLAN ID is assigned to logical NIC B 1818 for Tenant #2.When a packet is communicated from VM1 1806, a tag assigned to Tenant #1is attached to the packet by the hypervisor and the packet is thencommunicated from host machine 1802 to NVD 1812 over link 1814. In asimilar manner, when a packet is communicated from VM2 1808, a tagassigned to Tenant #2 is attached to the packet by the hypervisor andthe packet is then communicated from host machine 1802 to NVD 1812 overlink 1814. Accordingly, a packet 1824 communicated from host machine1802 to NVD 1812 has an associated tag 1826 that identifies a specifictenant and associated VM. On the NVD, for a packet 1824 received fromhost machine 1802, the tag 1826 associated with the packet is used todetermine whether the packet is to be processed by VNIC-VM1 1820 or byVNIC-VM2 1822. The packet is then processed by the corresponding VNIC.The configuration depicted in FIG. 18 enables each tenant's computeinstance to believe that they own their own host machine and NIC. Thesetup depicted in FIG. 18 provides for I/O virtualization for supportingmulti-tenancy.

FIG. 19 depicts a simplified block diagram of a physical network 1900according to certain embodiments. The embodiment depicted in FIG. 19 isstructured as a Clos network. A Clos network is a particular type ofnetwork topology designed to provide connection redundancy whilemaintaining high bisection bandwidth and maximum resource utilization. AClos network is a type of non-blocking, multistage or multi-tieredswitching network, where the number of stages or tiers can be two,three, four, five, etc. The embodiment depicted in FIG. 19 is a 3-tierednetwork comprising tiers 1, 2, and 3. The TOR switches 1904 representTier-0 switches in the Clos network. One or more NVDs are connected tothe TOR switches. Tier-0 switches are also referred to as edge devicesof the physical network. The Tier-0 switches are connected to Tier-1switches, which are also referred to as leaf switches. In the embodimentdepicted in FIG. 19 , a set of “n” Tier-0 TOR switches are connected toa set of “n” Tier-1 switches and together form a pod. Each Tier-0 switchin a pod is interconnected to all the Tier-1 switches in the pod, butthere is no connectivity of switches between pods. In certainimplementations, two pods are referred to as a block. Each block isserved by or connected to a set of “n” Tier-2 switches (sometimesreferred to as spine switches). There can be several blocks in thephysical network topology. The Tier-2 switches are in turn connected to“n” Tier-3 switches (sometimes referred to as super-spine switches).Communication of packets over physical network 1900 is typicallyperformed using one or more Layer-3 communication protocols. Typically,all the layers of the physical network, except for the TORs layer aren-ways redundant thus allowing for high availability. Policies may bespecified for pods and blocks to control the visibility of switches toeach other in the physical network so as to enable scaling of thephysical network.

A feature of a Clos network is that the maximum hop count to reach fromone Tier-0 switch to another Tier-0 switch (or from an NVD connected toa Tier-0-switch to another NVD connected to a Tier-0 switch) is fixed.For example, in a 3-Tiered Clos network at most seven hops are neededfor a packet to reach from one NVD to another NVD, where the source andtarget NVDs are connected to the leaf tier of the Clos network.Likewise, in a 4-tiered Clos network, at most nine hops are needed for apacket to reach from one NVD to another NVD, where the source and targetNVDs are connected to the leaf tier of the Clos network. Thus, a Closnetwork architecture maintains consistent latency throughout thenetwork, which is important for communication within and between datacenters. A Clos topology scales horizontally and is cost effective. Thebandwidth/throughput capacity of the network can be easily increased byadding more switches at the various tiers (e.g., more leaf and spineswitches) and by increasing the number of links between the switches atadjacent tiers.

In certain embodiments, each resource within CSPI is assigned a uniqueidentifier called a Cloud Identifier (CID). This identifier is includedas part of the resource's information and can be used to manage theresource, for example, via a Console or through APIs. An example syntaxfor a CID is:

ocid1.<RESOURCE TYPE>.<REALM>.[REGION][.FUTURE USE].<UNIQUE ID>

-   -   where,    -   ocid1: The literal string indicating the version of the CID;    -   resource type: The type of resource (for example, instance,        volume, VCN, subnet, user, group, and so on);    -   realm: The realm the resource is in. Example values are “c1” for        the commercial realm, “c2” for the Government Cloud realm, or        “c3” for the Federal Government Cloud realm, etc. Each realm may        have its own domain name;    -   region: The region the resource is in. If the region is not        applicable to the resource, this part might be blank;    -   future use: Reserved for future use.    -   unique ID: The unique portion of the ID. The format may vary        depending on the type of resource or service.

Although specific embodiments of the disclosure have been described,various modifications, alterations, alternative constructions, andequivalents are also encompassed within the scope of the disclosure.Embodiments of the present disclosure are not restricted to operationwithin certain specific data processing environments, but are free tooperate within a plurality of data processing environments.Additionally, although embodiments of the present disclosure have beendescribed using a particular series of transactions and steps, it shouldbe apparent to those skilled in the art that the scope of the presentdisclosure is not limited to the described series of transactions andsteps. Various features and aspects of the above-described embodimentsmay be used individually or jointly.

Further, while embodiments of the present disclosure have been describedusing a particular combination of hardware and software, it should berecognized that other combinations of hardware and software are alsowithin the scope of the present disclosure. Embodiments of the presentdisclosure may be implemented only in hardware, or only in software, orusing combinations thereof. The various processes described herein canbe implemented on the same processor or different processors in anycombination. Accordingly, where components or modules are described asbeing configured to perform certain operations, such configuration canbe accomplished, e.g., by designing electronic circuits to perform theoperation, by programming programmable electronic circuits (such asmicroprocessors) to perform the operation, or any combination thereof.Processes can communicate using a variety of techniques including butnot limited to conventional techniques for inter process communication,and different pairs of processes may use different techniques, or thesame pair of processes may use different techniques at different times.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that additions, subtractions, deletions, and other modificationsand changes may be made thereunto without departing from the broaderspirit and scope as set forth in the claims. Thus, although specificdisclosure embodiments have been described, these are not intended to belimiting. Various modifications and equivalents are within the scope ofthe following claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected” is to be construed as partly or wholly contained within,attached to, or joined together, even if there is something intervening.Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein can beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein, isintended merely to better illuminate embodiments of the disclosure anddoes not pose a limitation on the scope of the disclosure unlessotherwise claimed. No language in the specification should be construedas indicating any non-claimed element as essential to the practice ofthe disclosure.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is intended to be understoodwithin the context as used in general to present that an item, term,etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y,and/or Z). Thus, such disjunctive language is not generally intended to,and should not, imply that certain embodiments require at least one ofX, at least one of Y, or at least one of Z to each be present.

Preferred embodiments of this disclosure are described herein, includingthe best mode known for carrying out the disclosure. Variations of thosepreferred embodiments may become apparent to those of ordinary skill inthe art upon reading the foregoing description. Those of ordinary skillshould be able to employ such variations as appropriate and thedisclosure may be practiced otherwise than as specifically describedherein. Accordingly, this disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the disclosure unless otherwise indicated herein.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

In the foregoing specification, aspects of the disclosure are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the disclosure is not limited thereto. Variousfeatures and aspects of the above-described disclosure may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

What is claimed is:
 1. A system comprising: a network headend devicecomprising a processor, wherein the network headend device is configuredto: receive a first key provisioned by a customer; receive a first datapacket sent from a device of the customer; and decrypt the first datapacket using the first key to obtain information; and a networkvirtualization device, comprising: a memory device configured to store asecond key, wherein the second key is a crypto key; and a cryptoprocessor configured to encrypt and/or decrypt data using the secondkey, wherein the network virtualization device is configured to: receivethe information from the network headend device, after the first datapacket is decrypted; ascertain that the information is to be sent to avirtual machine in a virtual cloud network; ascertain that data in thevirtual cloud network is configured to be encrypted; encrypt theinformation with the second key to generate a second data packet; androute the second data packet to the virtual machine, wherein the networkvirtualization device is associated with a host, and wherein the hostdoes not have access to the first key or to the second key.
 2. Thesystem of claim 1, wherein the network headend device is configured tobe a termination point of an internet protocol security (IPSec) tunnelformed between the network headend device and a customer device.
 3. Thesystem of claim 1, wherein the first data packet is routed through thepublic Internet.
 4. The system of claim 1, wherein the first data packetis routed through a set of private links, without using links in thepublic Internet.
 5. The system of claim 1, wherein the networkvirtualization device supports an instance of the virtual machine in thevirtual cloud network.
 6. The system of claim 1, wherein the networkheadend device is a network interface card.
 7. The system of claim 1,wherein the network headend device is on a network interface card andthe network virtualization device is part of the network interface card.8. The system of claim 1, wherein the network headend device and thenetwork virtualization device are in the same server.
 9. The system ofclaim 1, wherein the network headend device is dedicated to thecustomer, such that no other customers of a host use the network headenddevice.
 10. The system of claim 1, wherein the network virtualizationdevice communicates with a key management service to obtain the secondkey.
 11. The system of claim 1, wherein the customer provisions thefirst key in the network headend device using a key management service.12. The system of claim 1, wherein the network headend device is a firstnetwork headend device and the system further comprises a second networkheadend device configured to decrypt data from the customer.
 13. Thesystem of claim 1, wherein: the network virtualization device is a firstnetwork virtualization device; the virtual cloud network is a firstvirtual cloud network; the system further comprises a second networkvirtualization device; and the second network virtualization device isconfigured to receive data from the network headend device and encryptdata received from the network headend device for a second virtual cloudnetwork using a third key.
 14. The system of claim 13, wherein the firstnetwork virtualization device and the second network virtualizationdevice are part of the same network interface card.
 15. The system ofclaim 1, wherein the network headend device is configured to receive thefirst key from the customer after a host authenticates the customer. 16.A method comprising: receiving, using a network headend device, a firstkey provisioned by a customer; receiving a first data packet at thenetwork headend device sent from a device of the customer; decryptingthe first data packet, using the first key, to obtain information;receiving, using a network virtualization device, the information fromthe network headend device, the network virtualization devicecomprising: a memory device configured to store a second key, whereinthe second key is a crypto key; and a crypto processor configured toencrypt and/or decrypt data using the second key; ascertaining that theinformation is to be sent to a virtual machine in a virtual cloudnetwork; encrypting the information with the network virtualizationdevice, using the second key, to generate a second data packet; androuting the second data packet to the virtual machine, wherein thenetwork virtualization device is associated with a host, and wherein thehost does not have access to the first key or to the second key.
 17. Themethod of claim 16 wherein the method comprises ascertaining that datain the virtual cloud network is configured to be encrypted beforeencrypting the information using the second key.
 18. A non-transitorycomputer-readable memory storing a plurality of instructions executableby one or more processors, the plurality of instructions comprisinginstructions that when executed by the one or more processors cause theone or more processors to perform processing comprising: receiving,using a network headend device, a first key provisioned by a customer;receiving a first data packet at the network headend device sent from adevice of the customer; decrypting the first data packet, using thefirst key, to obtain information; receiving, using a networkvirtualization device, the information from the network headend device,the network virtualization device comprising: a memory device configuredto store a second key, wherein the second key is a crypto key; and acrypto processor configured to encrypt and/or decrypt data using thesecond key; ascertaining that the information is to be sent to a virtualmachine in a virtual cloud network; encrypting the information with thenetwork virtualization device, using the second key, to generate asecond data packet; and routing the second data packet to the virtualmachine, wherein the network virtualization device is associated with ahost, and wherein the host does not have access to the first key or tothe second key.
 19. The non-transitory computer-readable memory of claim18, wherein the plurality of instructions further comprises instructionsthat when executed by the one or more processors cause the one or moreprocessors to perform processing comprising receiving the first datapacket over the public Internet.